Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-04-14 : 09:41:23
|
| Trevor writes "I have a simple VB app that uses ADO 2.7 to parse a database and email task reminders. The app runs as expected when invoked directly. However, it logs the error "File name or class name not found during Automation operation" when instantiating the ADODB.Connection class when run as a SQL Server Agent job.Also, when I remove the error handler and let the app raise the error, the SQL job runs indefinitely instead of stopping with a failure.Any ideas?Thanks!" |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2003-04-14 : 11:26:25
|
| Sounds like the ADODB DLL's/ MDAC components aren't installed on the server....when jobs/proces are run directly via QA...they run locally on your PC....however when they are run via the SQL Agent, they run on the server.... |
 |
|
|
testit01
Starting Member
1 Post |
Posted - 2003-04-14 : 13:18:14
|
| Yes, that's what the error would seem to indicate, but this is not the issue. MDAC 2.7 is installed on the server. The executable runs successfully when directly invoked ON THE SERVER (i.e. double-clicking the .exe file while logged into the server). However, the error is logged when the executable is launched from the SQL job. Query Analyzer is not involved in any way.I thought that it might be a permissions issue since this is really the only difference I can see between running the executable directly and running it through a SQL job. However, my user and the user that SQL Server Agent runs under belong to exactly the same groups.Any other ideas? |
|
|
|
|
|
|
Executable gives automation error running as SQL Server Agent job