Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts

Thursday, March 22, 2012

error: 26 - Error Locating Server/Instance Specified

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Does anyone know what could be wrong ?

Check if the local/remote connections have been enabled for ur instamce....Launcg SQL Server Surface Area configuration...Connections and services...Check Local and Network connections.....|||Looks like you are trying to connect a remote named instance. To make it work, SQL Browser on the remote server must be enabled, UDP port 1434 should be put into exception if firewall presents.|||

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

|||

Naeem Sheikh wrote:

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

Thnanks i wonder firewall is blocking my tcp/ip port and now i am connecting to the server|||Yes. It that is necessary.

error: 26 - Error Locating Server/Instance Specified

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Does anyone know what could be wrong ?

Check if the local/remote connections have been enabled for ur instamce....Launcg SQL Server Surface Area configuration...Connections and services...Check Local and Network connections.....|||Looks like you are trying to connect a remote named instance. To make it work, SQL Browser on the remote server must be enabled, UDP port 1434 should be put into exception if firewall presents.|||

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

|||

Naeem Sheikh wrote:

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

Thnanks i wonder firewall is blocking my tcp/ip port and now i am connecting to the server|||Yes. It that is necessary.

error: 26 - Error Locating Server/Instance Specified

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Does anyone know what could be wrong ?

Check if the local/remote connections have been enabled for ur instamce....Launcg SQL Server Surface Area configuration...Connections and services...Check Local and Network connections.....|||Looks like you are trying to connect a remote named instance. To make it work, SQL Browser on the remote server must be enabled, UDP port 1434 should be put into exception if firewall presents.|||

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

|||

Naeem Sheikh wrote:

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

Thnanks i wonder firewall is blocking my tcp/ip port and now i am connecting to the server|||Yes. It that is necessary.

error: 26 - Error Locating Server/Instance Specified

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Does anyone know what could be wrong ?

Check if the local/remote connections have been enabled for ur instamce....Launcg SQL Server Surface Area configuration...Connections and services...Check Local and Network connections.....|||Looks like you are trying to connect a remote named instance. To make it work, SQL Browser on the remote server must be enabled, UDP port 1434 should be put into exception if firewall presents.|||

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

|||

Naeem Sheikh wrote:

I installed SQL Server 2005 and I unable to connect my client Machine. I Created a DSN to connect to the Database through ODBC. Locally I am testing and everything works fine. The error is “SQL Server not Exist or Access Denied” on a client machine. I m using SQL server authentication with Mix mode installation and default Instance name as the Machine Name. If, I connect through Windows Authentication mode then it shows the Error “General Network Error contact to Network Administrator Documentation” On client machine I am also connecting through Visual Studio 2005 Server Explorer but connection showing no database. What should I do to connect my client machine? If I create a New SQL Server Database Name in Server Explorer of Visual Studio 2005 it will give the Error Message “under the Default Setting SQL Server does not allow remote connection Network (provider: SQL Network Interface, Error: 26 – Error Locating Server / Instance Specified)

I already change the Remote Connection to Local & Remote Connection and choosing Option Use TCP/IP. But not succeeded

THANKS IF ANY BODY SOLVE MY PROBLEM

Thnanks i wonder firewall is blocking my tcp/ip port and now i am connecting to the server|||Yes. It that is necessary.

Wednesday, March 21, 2012

Error: 18456, Severity: 14, State: 12.

I am running SQL Server 2005 x64 SP2 and have problem connecting to database with the SQL logins I created. I test the database login using Microsoft ODBC Administrator to connect the the database locally, only 'sa' can login. All other sql logins I created fails and returns this message:


Microsoft SQL Server Login

Connection failed:
SQLState: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'doteasylogin'.


OK

In the SQL Logs, it shows: Error: 18456, Severity: 14, State: 12.

The SQL Services is running as 'Local System'.

Can anyone help please?

Did you create the user at the server level and give him access to the server (and to the database) ? The state 12 indicates that there is an access problem which is normally dedicated to the fact that the user is either not allowed to login or does not have the appropiate permissions for the database.


Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I created the user 'testlogin' in SQL Server Login and grant the 'testlogin' user db_datareader & db_datawriter permission in Database Role Membership.

I'm using Windows Server 2003 x64 standard edition.

|||

Try executing the following two queries and check that each of them returns a row:

select name, principal_id from sys.server_principals where name = 'testlogin'

select permission_name, state_desc from sys.server_permissions where grantee_principal_id = suser_id('testlogin')

The first query should return the 'testlogin' login name and its associated id.

The second query should display a row with the CONNECT_SQL, GRANT value.

Thanks

Laurentiu

|||

Hello.

I have the same problem.

I am a beginner in SQL Server.I tried to install SQLServerExpress2005sp2

I've migrated a database from Access.

I tried to make a new user: for example 'testlogin' .

I've do all you sugest (server permissions, database permissions, ..)

I've run the queries from above and everything seems ok, but I cannot connect to database using the 'testlogin' account.

Error: 18456, Severity: 14, State: 12.

Login failed for user 'testlogin'. [CLIENT: xx.xx.xx.xxx]

IMPORTANT: if I grant sysadmin role to 'testlogin' I can connect.

thanks a lot in advance.

|||I started receiving this error after attempting to set up database mirroring. After running through the configuration including setting up endpoints (unsuccessfully) the mirror server has stopped accepting logins from SQL accounts (except SA). The principal server still accepts SQL logins without failure. I have stopped mirroring and deleted the database on both servers. Thank you for any help you can give. This was not an issue before I attempted database mirroring.

Okay after looking at it further it turned out that in my instance there was a new object for mirroring created. This object was accessible by going to the properties of the user account, choosing securables on the left side of the window. Then click on the add button and choose "all objects of the types" click OK; check Endpoints and click OK. In my case I saw the "Mirroring" option under Securables. That seems to be the culprit, after selecting Grant for the Connect permission I was able to connect fine. As a temporary solution I have chosen to follow the steps mentioned before using the "Public" server role, that way all accounts will have connect access. This is just temporary until I learn how to Drop the pesky Mirroring object from the server altogether.
|||

I am having the same issue, create a login using TSQL and granting access to a user database and it will not connect. I have tried the queries mentioned and from sys.server_permissions is saying CONNECT SQL with the GRANT option.

As soon as I added the user to the sysadmin server role, no problems connecting.

Thank you.

Error: 18456, Severity: 14, State: 12.

I am running SQL Server 2005 x64 SP2 and have problem connecting to database with the SQL logins I created. I test the database login using Microsoft ODBC Administrator to connect the the database locally, only 'sa' can login. All other sql logins I created fails and returns this message:


Microsoft SQL Server Login

Connection failed:
SQLState: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'doteasylogin'.


OK

In the SQL Logs, it shows: Error: 18456, Severity: 14, State: 12.

The SQL Services is running as 'Local System'.

Can anyone help please?

Did you create the user at the server level and give him access to the server (and to the database) ? The state 12 indicates that there is an access problem which is normally dedicated to the fact that the user is either not allowed to login or does not have the appropiate permissions for the database.


Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I created the user 'testlogin' in SQL Server Login and grant the 'testlogin' user db_datareader & db_datawriter permission in Database Role Membership.

I'm using Windows Server 2003 x64 standard edition.

|||

Try executing the following two queries and check that each of them returns a row:

select name, principal_id from sys.server_principals where name = 'testlogin'

select permission_name, state_desc from sys.server_permissions where grantee_principal_id = suser_id('testlogin')

The first query should return the 'testlogin' login name and its associated id.

The second query should display a row with the CONNECT_SQL, GRANT value.

Thanks

Laurentiu

|||

Hello.

I have the same problem.

I am a beginner in SQL Server.I tried to install SQLServerExpress2005sp2

I've migrated a database from Access.

I tried to make a new user: for example 'testlogin' .

I've do all you sugest (server permissions, database permissions, ..)

I've run the queries from above and everything seems ok, but I cannot connect to database using the 'testlogin' account.

Error: 18456, Severity: 14, State: 12.

Login failed for user 'testlogin'. [CLIENT: xx.xx.xx.xxx]

IMPORTANT: if I grant sysadmin role to 'testlogin' I can connect.

thanks a lot in advance.

|||I started receiving this error after attempting to set up database mirroring. After running through the configuration including setting up endpoints (unsuccessfully) the mirror server has stopped accepting logins from SQL accounts (except SA). The principal server still accepts SQL logins without failure. I have stopped mirroring and deleted the database on both servers. Thank you for any help you can give. This was not an issue before I attempted database mirroring.

Okay after looking at it further it turned out that in my instance there was a new object for mirroring created. This object was accessible by going to the properties of the user account, choosing securables on the left side of the window. Then click on the add button and choose "all objects of the types" click OK; check Endpoints and click OK. In my case I saw the "Mirroring" option under Securables. That seems to be the culprit, after selecting Grant for the Connect permission I was able to connect fine. As a temporary solution I have chosen to follow the steps mentioned before using the "Public" server role, that way all accounts will have connect access. This is just temporary until I learn how to Drop the pesky Mirroring object from the server altogether.
|||

I am having the same issue, create a login using TSQL and granting access to a user database and it will not connect. I have tried the queries mentioned and from sys.server_permissions is saying CONNECT SQL with the GRANT option.

As soon as I added the user to the sysadmin server role, no problems connecting.

Thank you.

Friday, March 9, 2012

Error, while connecting with SQL Server 2005 express edition

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact under the default settings of SQL SERver does not allow remote connections.
(provider:Named Pipes Provider, error: 40-Could not open a connection to SQL Server)

Hi,

Did you enabled setting to allow remote connection? Please see the blog for setup Remote connection

http://blogs.msdn.com/sqlexpress/

Hope that helps,

Lan

|||abrahampackiaraj
thank you, I already verified the tick mark in the check box of"allow remote connections" and I restarted the system. but this errorfollows up|||

did you manage to solve this problem as i have the same issue

Thanks

|||but while installing asp.net 2.0 , it doesn't even ask for that option. where from i can get that...|||whre from you got the option to tick the check box of "allow remote connections", i dont find that..|||

You can find it in SQL Server Surface Area Configuration. You may take a look at this post:

http://forums.asp.net/thread/1347652.aspx

Sunday, February 26, 2012

Error with establishing a connection to the server

i cannot access my database as i am keep getting the following error:

"When connecting to SQL server 2005, this failure may be caused by the fact that under the default settings SQL server does not allow remote connections. (provider:shared memory provider, error: 40 - could not open a connection to SQL server)"

when i click on the properties window i cannot see my table nor can i make a new connection as the same error is shown, could you please advice me how i can fix this?

Make sure the SQL Server 2005 service is running.

Are you able to connect to the server through Query Analyzer ?

Visitwww.connectionstrings.com to know how to build a connection string for your scenario.

Friday, February 24, 2012

Error while trying to connect to another SQL Server Express machine

The error states:

Additional Information:
An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that unthe default settings SQL Server does not allow remote connections.

How do I correct this issue?

Thanks,

Steve C.

By default, SQL Server 2005 Express Edition disables network access / remote connections. This is for security purposes. We want this enabled explicitly should someone have a need for it. Here is a KB article that talks about ways to enable remote connections http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b914277

Thank You

Ajay

Wednesday, February 15, 2012

Error while establishing connection with sql server 2005 express

An error has occurred while establishing a connection to the server.
When connecting to SQL server 2005, this failure may be caused by the
fact that under the default settings SQL server does not allow remote
connections. [provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server]

the above was my error and i got a solution from y71chen as below

Problem solved...it turn out that in ASP.NET SQL server setup wizard when it asks for server name, I have to specifiy theinstance name as well as the server name when MS refer to "Server Name" they really mean "Server Instance Name") eg if your server was named 'bigturnip' then you need to specify 'bigturnip\sqlexpress' (where sqlexpress is the instance name - this one just happens to be the default used by SQL Server 2005 SQLExpress). By default the server name was entered as merely "bigturnip" but after i added "\sqlexpress", then everything worked. If anyone else is having this remote connection problem and when they did select remote connection and still does not work this is the way to solve the problem....

but my doubt is do i want to install my software again for specifying the instance name along with the server name or where can i go and specify the instance name.

regards

kalyan

Which software do you want to re-install? Are you referring to VS2005? I remember that there is not step during the installtion of VS2005 that allows you to specify the instance name for SQL Express; and the instance name is default to SQLExpress, while the server name is your computer name which can not be assigned other string.|||

i had the same problem as you describe above but still when i added \sqlexpress to my connection string, i got the error below. Help please.

Cannot open database "mydatabase.mdf" requested by the login. The login failed.
Login failed for user 'domain\myusername'.

Error While connecting to SQL Server

i have an Error While connecting to My SQL Server Express

just when i click add new data source i have an error msg as shown in this pic :

Plz Help Me ,,,

This seems to be a problem with VS, not SQL Express, according to this post. Check that out and see if it helps.

Mike

Error while connecting to DB through Public IP

While connecting to the DB through a public IP from my system i'm getting an SQL Server does not exist or access denied.But while using localhost its working fine.DB setting in the web.config file.The Code is

<!-- application specific settings -->
<appSettings>
<!-- <add key="connString" value="data source=10.1.1.228;initial catalog=ACE;password=XXXX;persist security info=True;user id=sa;packet size=4096" />-->
<add key="connString" value="packet size=4096;user id=sa;data source=EBIZ;persist security info=True;initial catalog=ACE;password=password" />
</appSettings>

What to do for this error.Did you try following the connection string advice athttp://www.connectionstrings.com?

Terri

Error while connecting to analysis services data source from reporting services

  • I am trying to connect to an analysis services data source from reporting services.
  • Analysis services is on a different domain. When I try to run the reports I get the error
  • "Non-Windows user credentials were supplied for a non-http connection to Analysis Services. The Microsoft SQL Server Analysis Services data extension requires Windows Integrated Security unless connecting via http or https. "
  • Any ideas on what is the workaround?

    Try this:

    on the reporting server, create a user ie. report and in IIS let the Reports and Reportserver run as the report user you just created. On the Analysis server, create that same user with the same password. Add that user to the Analysis cube. Thats it.

    I have added my report user on the domain and also locally on the server. I don't think you need the user in both places but you can test as a local user as see what happens

    |||When I modified the user in the report server application poll, I'm getting "service unavailable" error when connecting to reports|||

    Leave the app pool as Network Service,

    In IIS, Report/Reportserver properties ->directory security, check enable anonymous access and type in your user name and password

  • Error while connecting Analysis Manager

    Hi,

    I try to connect a distant analysis manager server. My user is declared as Administrators in the distant server. I'm Administartor too on my PC

    When I try to connect this server (via IP adress) a error appears :

    Cannot connect to the repository

    Analysis server : ip adress here

    Error:
    '\\<nameOfDistantServer>\MSOLAPRepository$\msdrep.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on wich the file resides.

    Someone can help me ?

    Thanks

    moustachuRefer to the registry for the key [HKLM\Software\Microsoft\OLAP Server\Server ConnectionInfo\RemoteRepositoryConnectionString] and edit the value with the valid path.|||I will try as soon as possible

    Thanks

    Error while connecting after restarting the PC

    Hi,

    I am running SQL Server Enterprise manager. I was able to connected to the database properly. But after restarting the PC I am getting the following error.

    "System.NullReferenceException: Object reference not set to an instance of an object"

    The following event where logged in event viewer.

    under security: 560, 562, 538, 528.

    under system: 7035, 7036

    could anbody give hint how to solve this issue?

    Do you have the call stack for the exception? If so, can you post it here. It might be helpful to identify the issue.

    Thanks,

    Junfeng

    |||

    Hi,

    Thanks for taking interest.Please see the description below.

    We are using the tool sequencer. which will be running in the client & server.

    It will get informations from the sql server database.

    There is a field in database to set the PCID. I don't know, there is some problem in updating the PCID field in database.

    See the below call stack exceptions.

    I am not getting this problem from all the PC. I am able to access sucessfully from 2 PC. (Any how I haven't restarted these PC's).

    04 May 2007 12:10:39,841 [2676] INFO Sequencer.Backend.Perspective.Configuration (null) - Set active database to server=BLRKCCBD.in002.siemens.net;Integrated Security=SSPI;database=Sequencer VIL DB
    04 May 2007 12:10:39,841 [2676] INFO Sequencer.Backend.Perspective.Configuration (null) - Set language to english
    04 May 2007 12:10:39,841 [2676] INFO Sequencer.Backend.Perspective.Configuration (null) - Set testling version to IMP version 01.02.01.T208 at 09.06.2005
    04 May 2007 12:10:47,435 [2676] FATAL Sequencer.Backend.DBAccess.TestElementPool (null) - Error setting PCID for user.
    System.NullReferenceException: Object reference not set to an instance of an object.
    at Sequencer.Backend.DBAccess.UserPool.SetUserPCID(String pcid)
    04 May 2007 12:10:47,716 [2676] FATAL Sequencer.Backend.DBAccess.TestElementPool (null) - Error on loading TestElement data.
    System.Exception: error: > System.NullReferenceException: Object reference not set to an instance of an object.
    at Sequencer.Backend.DBAccess.UserPool.SetUserPCID(String pcid)
    End of inner exception stack trace
    at Sequencer.Backend.DBAccess.UserPool.SetUserPCID(String pcid)
    at Sequencer.Backend.DBAccess.UserPool.GetInstance(Int32 dbId)
    at Sequencer.Backend.DBAccess.TestElementPool.LoadData(Int32 dbId)
    04 May 2007 12:12:44,728 [2676] FATAL Sequencer.UI.MainWindow (null) - Error in system
    System.Exception: Error during startup!! > System.Exception: error: > System.Exception: error: > System.NullReferenceException: Object reference not set to an instance of an object.
    at Sequencer.Backend.DBAccess.UserPool.SetUserPCID(String pcid)
    End of inner exception stack trace
    at Sequencer.Backend.DBAccess.UserPool.SetUserPCID(String pcid)
    at Sequencer.Backend.DBAccess.UserPool.GetInstance(Int32 dbId)
    at Sequencer.Backend.DBAccess.TestElementPool.LoadData(Int32 dbId)
    End of inner exception stack trace
    at Sequencer.Backend.DBAccess.TestElementPool.LoadData(Int32 dbId)
    at Sequencer.Backend.DBAccess.TestElementPool.GetInstance(Int32 dbId)
    at Sequencer.Backend.DBAccess.TestElementPool.GetInstance(String dbName)
    at Sequencer.UI.MainWindow.GetInstance()
    End of inner exception stack trace
    at Sequencer.UI.MainWindow.GetInstance()
    at Sequencer.UI.MainWindow.Main()


    Kind Regards

    Siva.P

    error while connecting

    Hey all,

    I am new to ASP.NET. While executing a simple code , i got the error:System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

    Whats wrong?

    Regards

    Yasir

    Maybe the problem is in your connection string or you don't open database connection when executing data manipulating.Please check this again.If you still have a problem.please paste your code here.

    Error while configuring

    While configuring reporting services, in the database setup section, I am entering the instance name connecting to, and the user-id details. On applying the changes, i am getting an error that "Using other edition of database for reporting data sources and/or report server databases is not allowed in this version of Reporting services"

    Can anyone help me resolve this issue?

    Thanks,

    Vijay

    Are you trying to connect to SQL Server 2005 express edition from your reporting services whose edition is not from express edition?

    Shyam

    |||I tried using both express instance and default instance. Both are giving the same error.|||

    When you say default, it may also mean Developer edition. Ensure that you have an enterprise or a standard edition on your database server and connect to that instance.

    Shyam

    |||

    We are using standard edition. Won't reporting services not work with standard edition?

    Thanks,

    Vijay

    |||Is the reporting services edition on your report server an express edition?