Moving solution to another machine, SQL Failure

  • Thread starter Thread starter Michael Jackson
  • Start date Start date
M

Michael Jackson

Hi all,

I've developed a .NET 2003/SQL Server 2000 application. When the app fires
up, it loads combo boxes (Using SQLDMO) with available servers, databases
and tables. It works great. However, when I move the solution to another PC
and try to run it, it fails saying "Login failed for user DEVONE\Guest'.
DEVONE is the name of the machine where I developed the application, which
is running SQL Server 2000 Developer.

No where in my code does it reference DEVONE, so somewhere a reference to
the previous machine name or SQL Server instance name is being held in the
solution.

Any ideas?

Thanks
Michael
 
Did you do a Find-in-Files on entire solution to look for DEVONE?

Regards,

Deepak
[I Code, therefore I am]
 
Entire Solution.

I guess what's happening is since the second PC is on the network, the
SQLDMO code is finding the developments machine instance of SQLServer,
DEVONE, but, it's not finding (local).

When I first put the compiled solution on the new PC, it worked fine.
Several times in fact. But without any changes of ANY SORT, it quit working.

I unplug the network cable from the new PC, now DEVONE is not found, but the
SQLDMO code is not finding the local instance of SQL (on the new PC).

Thanks.
Michael
Deepak said:
Did you do a Find-in-Files on entire solution to look for DEVONE?

Regards,

Deepak
[I Code, therefore I am]


Michael Jackson said:
Hi all,

I've developed a .NET 2003/SQL Server 2000 application. When the app
fires
up, it loads combo boxes (Using SQLDMO) with available servers, databases
and tables. It works great. However, when I move the solution to another
PC
and try to run it, it fails saying "Login failed for user DEVONE\Guest'.
DEVONE is the name of the machine where I developed the application,
which
is running SQL Server 2000 Developer.

No where in my code does it reference DEVONE, so somewhere a reference to
the previous machine name or SQL Server instance name is being held in
the
solution.

Any ideas?

Thanks
Michael
Click to expand...
Click to expand...
 
Back
Top