March 19, 2002 at 4:18 am
Hi,
I am trying to pick up on a unresolved issue that I logged previously. I am trying to schedule a DTS package that uses ActiveX script that calls a DLL. I have tested the DLL independantly on the SQL server where the package is running from. When just running the package it works fine, but when scheduling the package the DLL's CreateObject command does not want to execute correctly. I DID register the DLL correctly and it can be called independantly from the SQL Server. Is this a permission error ? Does the SQLAgent account not have the correct permissions to : CreateObject(MyDLL) ?
Please help, I am sure this is a problem a lot of DTS developers struggle with.
Regards,
Dirk
March 19, 2002 at 5:15 am
Sounds like a permissions error, and yes SQL Agent must have rights on the object in order to use. To test try logining in as SQL Agent on the box in question and running the package, if it will not let you then you know for sure it is the permissions (It should hopefully give you the same error it has been giving agent all this time when logged in that way as well, so even if not permissions with the object you will have a better idea).
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
March 19, 2002 at 5:22 am
Hi,
Thanks for the feedback. 2 Simple questions though.
1. What exactly is the SQLAgent logon account and how do I use this account to log onto the server, do I only start and stop the SQL service with this account ? Why can one not use the Administrator's account to run this successfully ?
2. How do I assign permissions of a DLL to a specific account like the SQLAgent account ?
Thanks again,
Dirk
March 19, 2002 at 6:12 am
1) This can be found by drilling down thru Enterprise Manager to SQL Server Agent under Management. Right click on SQL Server Agent and choose properties and the login will be defined on the General Tba, which I bet since you ask that it is set as System Account which should have all rights on the local server. So let's try this first.
Open the DTS package in design mode and select Package on the tool bar then select Properties. Now if this is SQL 7 you will want to be on the General Tba, if 2000 then the Logging Tab. You will find a boxed section labeled Error Handling with a text box for Error FIle and a Browse button. Click the button and find a place to create a text error log for this package, give it a name that will make sense. And set check on Write completion status to Event Log. Now start the job and let fail. When fails you shoudl be able to open the text error file and see what error messages are being returned. Try this and let us know what happens.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply