July 7, 2009 at 9:26 am
I am a user for SQL Server with Wonderware InTouch. InTouch is a process visualization tool. InTouch is using the SQL Server for the Alarmdatabases and recipe handling.
I want to add a few SQL-jobs to the server for deleting data which are older than one year. I tested all that on my office PC and it was running perfect.
Now I want to add the jobs to the server of the customer. To handle SQL jobs it is necessary to run the SQL-Server Agent. The SQL server agent will not start.
When I am starting the SQL Server Agent this massage is popping up:
Error connecting to the server. When connecting to SQL Server 2005 may cause this error are that the SQL Server default remote connections are not allowed. (provider: Named Pipes Provider, error: 40 - Connection with SQL Server could not be opened) (Microsoft SQL Server, Error: 53)
also when I will connect the SQL database from the customer with my office SQL Server this error is showing.
And this condition is since the customers PC got a new name and is connected to their domain.
Before there was no problem about this.
What must I do to get access to the SQL Server agent?
The Server is running on Win XP professional.
The SQL Server is SQL Server 2005
Microsoft SQL Server Management Studio9.00.3042.00
Microsoft Analysis Services Client Tools2005.090.3042.00
Microsoft Data Access Components (MDAC)2000.085.1132.00 (xpsp.080413-0852)
Microsoft MSXML2.6 3.0 4.0 6.0
Microsoft Internet Explorer7.0.5730.13
Microsoft .NET Framework2.0.50727.1433
Operating System5.1.2600
July 7, 2009 at 10:38 am
More than likely the issue is that when the PC was renamed/added to the client domain, any credentials that the SQL server Services were using have now become invalidated. For example, if the SQL Service was using a username of yourdomain\SqlUser and the machine was put into your client's domain (Clientdomain), when it tries to contact the Domain of Yourdomain to authenticate it fails because it only knows about the domain ClientDomain.
In other words, use the SQL Server Configuration Manager to make certain that the services are all using usernames and passwords that actually exist. Once that's done make sure the machine is allowing external connections, Make certain that Named Pipes and TCP/IP are enabled in the NEtwork connections section of the Configuration Manager.
-Luke.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply