sql error 15138: connection

Showing posts with label connection. Show all posts

Thursday, March 29, 2012

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to th
e
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'
Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'sql

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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'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?

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

|||

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:

|||

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

Thanks
Laurentiu

|||

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

Thanks

|||

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

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

|||

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 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:

SQL Server 2005:

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

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC call
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.
This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC ca
ll
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Sunday, March 11, 2012

Error 1203

I am running a script on a schedule and I get this error quite often:

Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000] (Error 0) Process ID ## attempted to unlock a resource it does not own: OBJECT: ## . Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator. [SQLSTATE HY000] (Error 1203)

If I keep rerunning the transaction, it will eventually succeed. I am running SQL Server 2005 with SP1 installed. Does anyone know what this means and what would cause it to fail sometimes and succeed other times?

Thanks

This often indicates some sort of corruption in your database. See BOL topic below for more details:

http://msdn2.microsoft.com/en-us/library/aa337285.aspx

|||

It does not appear to be any sort of corruption. The DBCC CHECKDB returned no errors. Are there any other things that could cause this besided database corruption?

Thanks.

|||In that case, you will have to contact PSS to open a case so they can investigate further. This can also be due to a bug in SQL Server lock manager code caused by your workload/configuration. Btw, if you haven't applied the latest service pack of SQL Server (SP1) and the cumulative hotfix please do that first to see if you can repro the problem.

Error -10535 SQL Server Connection Timed Out

We receive the following error in SQL 6.5 and I would like some help in getting it fixed.
Error -10535 SQL Server Connection Timed Out. We get this when a client dials in to run a query
All help is greatly appreciatedis this being done through a linked server?|||Originally posted by Memnoch1207
is this being done through a linked server?

No the application connects to the database through a SQL ODBC connection.|||What is the default net-library used to connect?|||Originally posted by Satya
What is the default net-library used to connect?

Sorry for the delay. It is TCP/IP

Friday, March 9, 2012

Error 10061, SQL Server 2005 DEV actively refuses connection

I just installed a fresh SQL Server 2005 MSDN and tried to use the
management console, but all attempts to logon fail.
Message says 'failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.'
How can I change these settings or otherwise get a connection?
Thanks.First is to open up the Surface Area Configuration tool, select to
view Services and Connections. Under Database Engine, go to Remote
Connections. Change it to allow remote connections using whichever
protocols you plan on using from remote clients.
-Sue
On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
wrote:

>I just installed a fresh SQL Server 2005 MSDN and tried to use the
>management console, but all attempts to logon fail.
>Message says 'failure may be caused by the fact that under the default
>settings SQL Server does not allow remote connections.'
>How can I change these settings or otherwise get a connection?
>Thanks.|||Worked. Thank you. New to 2005.
On Tue, 17 Apr 2007 11:45:22 -0600, Sue Hoegemeier
<Sue_H@.nomail.please> wrote:
[vbcol=seagreen]
>First is to open up the Surface Area Configuration tool, select to
>view Services and Connections. Under Database Engine, go to Remote
>Connections. Change it to allow remote connections using whichever
>protocols you plan on using from remote clients.
>-Sue
>On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
>wrote:
>

Error 0xC020209C in Flat File Connection Manager in SSIS

Hi,
I got this error in a Flat File connection manager, it was saying that the last column caused the disk I/O Buffer overflow, whereas the last column contains 188 characters at max.

Any Idea how to deal with it ?

Thanks,
FahadI set the type of Flat File Source object to Unicode and problem was no more. But I still wonder whats the reason of this error ?

Wednesday, March 7, 2012

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

error :40 pls help ASAP

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)

I am using SQL server Express 2005 on my local machine. And ASP.net 2.0 with C#.

SQL Server does not allow remote connections by default, if you want to connect remotely you will have to enable this feature. See the Screencast on my site for more information how to do this.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Note that the OP indicates that he is running it locally... Which is odd that it would be treating a local connection as remote.

Check the protocols under the SQL configuration tool and make sure named pipes isn't disabled.

|||Yes, I did enble all the features in SQL server Express, it allws remote conenction , TCP/IP and pipes,. I searched this problem here and did all the necessary things.
Still I get this error , please help . If I use my connection string from WEB.config i get following error

"............................................................................

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

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

and if I use my connection string in code , I get above error #40.

Please help.

My connection string in code look like this :

string connstr = "server=localhost; uid=myusername; pwd=mypassword; database=dabatabasename";

Please help ASAP.

thanks

|||

Your connection string is wrong, if you are using SQLServer Express, you will have to point to the Express instance:

string connstr = @."server=localhost\SQLExpress; uid=myusername; pwd=mypassword; database=dabatabasename";

Jens K. Suessmeyer

http://www.sqlserer2005.de

|||HI,

Thanks for the reply, I have modified conection String and it works ,

But I still not able to get it work from WEB.CONFIG file , Could you tell me what is the settings of WEB.CONFIG file for ASP.NET 2.0 . How can I get value of my connection String from WEB.CONFIG file.

Thanks,
|||

Could you please post the part of the connection string (if you use SQL Server authentication you can obfuscate the part with the password / username)

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||HI Jens,

Here is the code of my connection string:

string connstr = "server=serverName\\SQLEXPRESS; Provider=SQLOLEDB; uid=myusername; DRIVER=SQL Native Client; pwd=mypasswd; database=MyDatabaseName";

This works rightnow , if I use in each pages.

Please let me kow how can I put in WEB.config file and use it in my all ASP pages.

|||

Did you make sure that you wont need the double \ in the web-config file ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||HI,

My problem is I am not able to get a value of Any varialbles of Web.config file.

I need to know how to get a value of any varialbes from WEB.CONFIG file.

Jatin.
|||

The web.config file is part of your ASP.NET application, you would be better off asking this question in a forum target at Visual Web Developer Express rather that SQL Server. The web.config file is not part of SQL Express and most the folks in this forum don't use VWD.

Mike

|||

Any updates on that ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||HI,

I have not posted yet on ASP.NET site. could you give me web address for that forum?

Jatin.

Thursday, March 29, 2012

Error 18456 - ODBC connection failed for domain user account

Error 18456 - ODBC connection failed for domain user account

Error 18456 - ODBC connection failed for domain user account

Tuesday, March 27, 2012

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

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

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

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

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

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

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

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

Error 18452

Error 18452

Sunday, March 11, 2012

Error 1203

Error -10535 SQL Server Connection Timed Out

Friday, March 9, 2012

Error 10061, SQL Server 2005 DEV actively refuses connection

Error 0xC020209C in Flat File Connection Manager in SSIS

Wednesday, March 7, 2012

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

error :40 pls help ASAP

Object reference not set to an instance of an object.

sql error 15138

Blog Archive

About Me