I'm having a problem with the node name on SQL2K jobs on a veritas
cluster. We are using named instance on the sql server. All the jobs
I create are getting a source of node1\instance. This causes a
problem if the cluster fails to node2. However, if I change the
originating server in the sysjobs table to clustername\instance, I can
run the job successfully, but I cannot make any changes to the job...
I get the MSX server error that you get when the server name on the
job does not match the name of the physical server. Also, any new
jobs I create always get assigned the node1\instance (or
node2\instance if that is the active node).

My @@servername is clustername\instance.

Any suggestions on how I should be configured for everything to work
properly?

Michael,

SQL Server 2000 virtual server is not supported on any cluster other than MSCS. Do you see the same behaviour on a SQL 2K virtual server on Microsoft Cluster Server (MSCS)?

The originating_server column should have the value of your SQL Server virtual instance (the value that you get after running "select @@servername"). If the originating_server colum has node_name
\instance_name then definitely the jobs will fail on the second node. In a SQL Server 2000 virtual instance on MSCS, everything points to the virtual server and not the actual nodes.


Best Regards,

Uttam Parui
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