Showing posts with label sql2005. Show all posts
Showing posts with label sql2005. Show all posts

Thursday, March 29, 2012

Error 18456 Severity: 14 State 11 problem

I am installing diskeeper administrator on one server with at database on our sql2005 server. When I am trying to connect to the database the diskeeper software says verify username and password. I try to connect using windows authentication .And in the serverlog this error occurs

2006-11-27 15:04:56.01 Logon Login failed for user 'NB\Servername$'. [CLIENT: "Ipadress"]

2006-11-27 15:04:56.01 Logon Error: 18456, Severity: 14, State: 11.

When i try to connect with Sql server authentication, this error occurs in the log:

2006-11-27 15:48:35.46 Logon Login failed for user 'NB\SERVERNAME$'. [CLIENT: ipadress

]2006-11-27 16:04:22.94 Logon Error: 18456, Severity: 14, State: 16.

I have tried to disable filesharing, and run installation of diskeepper as the domain administrator. But the same error occurs.

Can anyone help me with this

Regards Oyvind

State 11 indicates an error determining the database to be used after authentication. This could happen if the database cannot be accessed for some reason. You could try to connect to the master database initially, to see if that works, then change context to the database that you normally use and see what error you encounter, if any.

However, I am not familiar with the diskeeper software and I don't understand its relation with SQL Server, so I'm not sure how to help you further.

Thanks
Laurentiu

|||

Diskeeper do not have any link with SQL Server in this case, and also it is no use in running for linked server related error.

What is the privilege for the account used on the linked server?

Refer to KBA http://support.microsoft.com/kb/889646 fyi.

|||

The privilege for the account is sysadmin.

The default database is master.

I also tried to connect with odbc, but the same error occurs

Regards

Oyvind

|||have you contacted the vendor in this case?|||

Correction to my previous post: the state discussion applies to state 16, not to state 11.

State 11 indicates a different problem.

What is strange is that, while you mention using Windows and SQL authentication, both connections appear to be attempted via Windows authentication, using the machine account credentials.

Best thing would be to check with the diskeeper customer support.

Tuesday, March 27, 2012

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

|||I had a similar problem after creating a new (SQL) logon. Having restarted the following services it was resolved:

SQL Server ($instancename)
SQL Server Browser

SQL Server Express 2005

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

sql

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Hi

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

login failed fo ruser ' '. This user is not associated with a trusted SQL Server connection.

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

Hi

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect


SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Friday, February 24, 2012

Error "Connection is busy with results for another command"

I have looked at other threads regarding errors similar to this, but I think mine is a bit different.

I am using SQL2005 Standard Edition and my application is coded with C# using ADO.Net. OLEDB connection is used. The error occurs when the application has only one thread accessing the database. It does not happen consistently, so it is very puzzling.

I am wondering if anyone could offer any tip to diagnose this.

Thanks in advance!

Have a look at this article: http://blogs.msdn.com/dataaccess/archive/2005/08/02/446894.aspx

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

===================================

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.


ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

===================================

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.


ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

===================================

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.


ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployme

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

===================================

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.


ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.