June 15, 2006 at 2:36 pm
Hello,
In a SQL Agent Job, when I try to add or edit a step to run a SSIS package I only get the error "The specified module could not be found. (Exception from HRESULT: 0x8007007E) (SqlManagerUI)".
Please let me know how to create a job to run a package. I tried posting this in the SSIS and SQL Server Agent forums but they were not the correct place for this question.
much appreciated!
Skål - jh
June 16, 2006 at 10:20 am
If you are running the RTM build install SSIS on the box. In SP1 we added the necessary SSIS components to the tools install (so long as you selected Client Components under the Advance option dialog during the RTM installation - selecting just Mgmt Studio doesn't install all of the components).
June 16, 2006 at 11:09 am
Thank you Dan.
I'm running SQL 2005 full install (sql, ssis, as, rs, all client tools, everything), with SP1, it and the SSIS packages are all on my local machine. All installers were from MSDN, I do know know if they were the RTM build or not, it was the released versions.
What is RTM?
much appreciated!
Skål - jh
June 16, 2006 at 2:55 pm
I am having the same problem. I found the problem documented in KB918760. I have tried everything but method 3 and will attempt it next. If anyone has any suggestions, please advise. I have full install of SQL2K5 w/all components w/SP1 applied running on a W2K3 x64 server. SQLAgent is configured to log on as domain account which also has sa rights on box.
I first started by copying my DTS pkgs from 2000 to 2005. I have them running in legacy mode just fine in jobs on 2005. I ran the Package Wizard (well after I cleaned up some trailing spaces on a few pkgs that caused the wizard to fail) on 1 package and it migrated fine. It runs OK in SSIS. But when I try to run from a SQL job, it fails and there is no informative errors in the view history logs. I have tried using credentials/proxy agent...still no luck. This is UGLY!!!
December 14, 2007 at 2:44 pm
RTM = release to manufacturing
December 14, 2007 at 10:20 pm
Does the job fail or does it go into suspend status? We had an issue the other day in our test environment where we could not schedule SSIS jobs to run. Turns out the SSIS subsystem was pointing to some invalid dlls. We found this KB the other day. http://support.microsoft.com/kb/914171
December 17, 2007 at 12:55 pm
If you are using the SQL manager remotely, try terminal servicing into the machine itself. (The issue started after I ran SP1 locally, but has not appeared on dedicated SQL Server boxes.)
I still have the issue with my local SQL management console, but once I deploy the jobs to the server, was able to create and run the job steps if I was logged into the remote server itself.
Hope this helps, know it's not a fix.
Hope you've found an answer.
Skål - jh
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply