September 6, 2006 at 6:09 am
Over several months I have created and run several DTS packages on our server. In the last day or so, I have been unable to create, edit or run any DTS packages, instead I get an error:
[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.
This problem applies both to DTS that I have created and those created by other people. I used to be able to edit all of these.
I am connecting to a remotely hosted Windows 2000 server running SQL 2000, via terminal services. I am trying to access the DTS through Enterprise Manager to which I am connected as sa. Both Windows and SQL have the latest patches.
No admin changes have been made to either Windows or SQL 2000 recently.
Everything else seems to work fine, I can access all the databases, create tables, databases etc.
None of my colleagues seem to have this problem, they can all edit & run all DTS. As far as I can tell, the access permissions for my windows user are the same as everyone elses and I'm logged in to SQL as sa. This would seem to suggest it has something to do with my Windows login, but I can't see how.
Any help or ideas greatly appreciated!
September 7, 2006 at 7:54 am
two things I'd check
1) Is sa passoword blank ? (below from BOL)
Note If a user attempts to connect to an instance of SQL Server providing a blank login name, SQL Server uses Windows Authentication. Additionally, if a user attempts to connect to an instance of SQL Server configured for Windows Authentication Mode by using a specific login, the login is ignored and Windows Authentication is used.
2) Try dropping your NT user or group from SQL (if you can). Try sa passoword then. Then readd to SQL and DBs and see if OK then.
September 7, 2006 at 8:17 am
Maybe try a new sysadmin account as well.
Are you going through a firewall? I wouldn't expect it, but I wonder if DTS Designer uses some different port.
September 8, 2006 at 2:41 am
Steve, Bernard, thanks for your answers. I managed to fix the problem by un-registering the server in Enterprise Manager and the re-registering it under the name (local) rather than the actual server name. Not an ideal solution, but it gets me round my current problem. It's very weird as my colleagues use the same DTS packages and all connect via remote desktop in the same way as I do, but didn't exhibit the problem.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply