Error 80004005 on launching DTS

Hi all. I have just migrated our DWH environment from one server to another, from a named instance to another one. When I run the DTS it works fine, but when I launch it by using a job (running dtsrun) it fails with the following error:

DTSRun: Loading... Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.

What can be the cause of this? thanks a lot.Do you mean a real job within sql server or are you using dtsrun as a command-line utility ?|||Originally posted by rnealejr
Do you mean a real job within sql server or are you using dtsrun as a command-line utility ?

I have a job with several steps. Each step is a call to DTSRUN, specifying user, password and DTS name. I have tried to run other DTSs: they work fine, but if I try to launch the job from any step it fails. My SQLAgent service is logged by using a domain admin user.|||Who is the owner of the job and what access does this user have within sql server ? Your connection object in the dts package - what are you using for the server name and type of authentification ?|||Originally posted by rnealejr
Who is the owner of the job and what access does this user have within sql server ? Your connection object in the dts package - what are you using for the server name and type of authentification ?

The job is owned by SA, and the connection object uses OLEDB Provider for SQL Server. The server name is "COLBTADWH02\DWH_DESA", given it is a named instance.|||Authentication is by SQL Server, using SA.|||Was this job/package part of the migration as well ?|||Originally posted by rnealejr
Was this job/package part of the migration as well ?

Yes, the job and the package existed in the original environment. It was migrated via GenerateScript, and then the script was edited to change the <server\instance> name.|||What happens if you create a new job for the same package ? What is the access level of the account that is running agent - also, have you tried to use sa instead of the domain account ?|||Originally posted by rnealejr
What happens if you create a new job for the same package ? What is the access level of the account that is running agent - also, have you tried to use sa instead of the domain account ?

I have already tried entire job deletion and recreation. Just moments ago, another scheduled job (created by scheduling a DTS) was launched and it worked fine. The agent-running account is a domain admin, and also a local admin.|||I just tried the following: scheduled the first step of the job (a call to DTSRUN) , which created a job. I launched this new job and it worked well. What can be different so a DTS-created job works and a manually created job does not?|||I finally solved the problem by installing SQL SP2, but I still would like to know what caused the error. I think it is not safe to fix this kind of problems only by updating/reinstalling software.

Error 62 When connecting with SSMS to a SQL Server 2000 named instance

Hello,

I get error 62 when trying to connect to a SQL Server 2000 named instance from SQL Server Management Studio. I can register and connect to other SQL Server 2000 instances

I've tried all the usual stuff, including enabling all the protocols from SQL Server configuration Manager.

Any thoughts. Your help is very appreciated.

Thanks

Kevin Lobo

Can you post the whole error msg? Is this a local or remote connection? What's the Service Pack of your SQL Server 2000? Make sure sql browser is on if you can. Also make sure sql browser and/or udp port 1434 is in exception list if you firewall is on.

Thanks,
Xinwei

So, actually error 26, not 62.

|||

Hello Xinwei,

Thanks. It is working now. The Browser was running but the firewall setting was on with 'Don't allow exceptions' checked. I unchecked it and its ok now.

many thanks.

Jut FYI, here is the entire error message:

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

Error 5 (Access Denied) and Named Pipes Provider error 40

Hello there,

I recently started having trouble with my local SQL Server 8.0 database server. When I try to start it with Enterprise Manager I get the following error:

An error 5 - (Access is denied) occured while performing this service operation on the MSSQLServer service.

Nothing showed up in the SQL Server error logs. If I try to connect to it using the SQL Server Management Studio that came with SQL Server 2005 I get the following (slightly more informative) message:

Cannot connect to (local) ... (provider: Named Pipes Provider, error 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

I'm not sure which log to look at in the MSSQL folders: MSSQL.1, MSSQL.2 or MSSQL.3.

Furthermore, if I manually start the MSSQLSERVER service, then I can connect just fine with the SQL Server 2005 Management Studio but still get the weird error message with SQL Server 8.0 Enterprise Manager.

Any ideas?

Thanks

Nevermind, I figured out that I had changed the name of my computer. I changed the name back and can now connect to the server just fine.