November 23, 2006 at 5:28 am
Dear all,
I had a happy sql 2000 instance and then added a sql 2005 instance alongside it. Since then a DTS scheduled job has hung at the same point where an activex script is called - it simply creates some empty files. If I run the step or the whole package its is fine but not when scheduled as a job. I don't believe it is permission etc. I logged on to the server as the account that runs the services and the same thing occurs. So to me it looks as if something to do with the 2005 instance is causing the error.
The script looks a bit like:
'**********************************************************************
' Visual Basic ActiveX Script
'************************************************************************
Dim lo_fso, lo_File
Set lo_fso = CreateObject("Scripting.FileSystemObject")
Set lo_File = lo_fso.OpenTextFile("\\violet\dataimport\test.txt", 2, true)
lo_File.Close
Thanks for your help.
November 23, 2006 at 8:11 am
Looks to me like a permission issue anyway...
Can you verify that the account used when running as a job still has permission to access \\violet\dataimport\test.txt ?
/Kenneth
November 23, 2006 at 8:15 am
Hello and thanks for your reply.
I can verify that i logged on to the server as the domain user that runs sql server agent and is can write to that directoy. It runs fine from within the dts package but just hangs without error when run through sql server agent.
November 23, 2006 at 8:35 am
I suspect you lot think i've lost the plot - but I knew it was nothing to do with permissions...a reboot fixed it!
November 23, 2006 at 8:52 am
Nothing like a good ol' three-finger to solve any problem.
(though, access tokens also gets reset/renewed during a reboot)
Anyway, glad you solved it!
=;o)
/Kenneth
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply