Problems executing SPs and Jobs.

Question

Post reply

Problems executing SPs and Jobs.

Ronald Burgmeijer

SSC Journeyman

Points: 85
More actions
August 3, 2004 at 2:16 am

#85939

Hi,
I recently created a new SQL-Server instance on a newly installed server.
Before, I runned SQL-Server 2000 (SP2) on a Windows 2000 Server system. Now I upgraded to Windows 2003 Server with SQL-Server 2000 (SP3a).
Now I have problems with executing jobs which contain references to local packages. The packages, when executed manually, run perfectly. Also references to networkshares in SP's don't work anymore.
I run the server and the agent on a network admin account, which is the same account that is logged onto windows. The network shares are accesible in windows, as are they when creating or manually executing a package.
Does anybody have a clue as to what could cause this problem?
Best Regards,
Ronald
August 6, 2004 at 8:00 am

This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Alamir SSCertifiable Points: 6085 More actions · Answer 1

I still think there is some bugs between Windows 2003 and SQL Server 2000

try to install all windows updates ..

Alamir Mohamed
Alamir_mohamed@yahoo.com

Ronald Burgmeijer SSC Journeyman Points: 85 More actions · Answer 2

Thanks, but we have all updates (Win2003 server and SS2000) installed... so that doesn't seem to be the problem... thanks anyway!

Alamir SSCertifiable Points: 6085 More actions · Answer 3

by the way, I know that Windows 2003 has MDAC 2.8 installed, but try to install MDAC 2.7 SP1 on all clients and server machines

Also .. do you install SQL Server Tyoical Or Full ? try to add any missing Components if it is not full installation

Alamir Mohamed
Alamir_mohamed@yahoo.com

Ronald Burgmeijer SSC Journeyman Points: 85 More actions · Answer 4

I did a full install... I also tried the downgrading of the MDAC to 2.7 but that also didn't change anything... could it be that a service doesn't have enough permissions? or perhaps a port should be opened?

The strangest thing is that while browsing on the server, I can access my networkmappings but once in the enterprise manager, I can't... even though SS is running under the same account as windows 2003...

matey SSCommitted Points: 1845 More actions · Answer 5

this looks like access problem (security) i think the account running sql server does not have the required permissions for sql server. so i would say check the level of permission of the account running sql server which should have sys. admin rights to sql server.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 6

Who is the job owner?

You shouldn't downgrade MDAC to lower version since MDAC 2.8 is the component of Windows 2003 and widely used by system.

Ronald Burgmeijer SSC Journeyman Points: 85 More actions · Answer 7

The job owner is the logged on account. Could it be that the protocol we use is responsible? We make use of Named Pipes.

In that case I'll upgrade it again... I didn't know that the OS made such extensive use of the MDAC.

Jomy John Thomas Mr or Mrs. 500 Points: 550 More actions · Answer 8

Hi

I think its mainly an access problem to the network resource. The user who is logged on to execute the job does not have access to the resource.

Try this round about.

Open the query analyzer as the same user who will be executing the said jobs. then run these commands

exec xp_cmdshell 'net use W: \\Computer\ShareName

exec xp_cmdshell 'dir W:'

See if u are able to connect to the network resource and get a mapped drive W: and also the second command should help u list it contents.

Sometimes the n/w resource might requires a user name or password. You can supply it using the flags provided with net command.

If this works, create it as the first task above the one that is currently giving error. after that make sure that any access to the mapped resource is through the mapped drive letter and not using the network name.

Hope this should solve your problem

Regards,

Jomy John Thomas

Your Guide to Admin and Design

ddraper SSC Journeyman Points: 97 More actions · Answer 9

I am having the same problem. xp_cmdshell on Windows 2003 cannot access a UNC path. The UNC path is valid and works fine from the command prompts. The SQL Server Service is running as the W2003 Administrator account so it has full privs.

Did anyone ever figure this out?

Thanks,

Don