Message Error Im002 Microsoft Odbc Driver
If test connection succeeds and your app fails then it is probably one of those awkward environment issues. Things to check -. Have you creates a System DSN or User DSN? If your application is running as a System Service then it will only able to read System DSNs (not User DSNs). Was the Driver installed for all users or just the installation user? I have seen instances where this has affected some drivers.
Use (an excellent tool for tracking down issues like this) If you haven't used Process Monitor - think of it as a sniffer for; file accesses, registry accesses and network access. That is - you will be able to determine whether there are any files or registry accesses that are failing or being blocked. Wondering again whether this is a 32/64bit issue? There are two ODBC administrators on 64bit machines.
C: Windows system32 odbcad32.exe 64bit Also through Control Panel c: Windows SysWOW64 odbcad32.exe 32bit If your application is 32bit then you need a 32bit ODBC Driver and have to create a 32bit ODBC data source. If your application is 64bit then, similarly, you need a 64bit ODBC Driver and have to create a 64bit ODBC data source. I am wondering whether your application is 32bit and hence cannot find the 64bit ODBC data source you have created. (NOTE: all of this is only applicable on 64bit Windows OSs.).
Hi SSISJoost, Am running the package in 32 bit mode only and it runs fine when manually executed from the sql agent but even runs fine if i schedule it to run after 30 min after the manual run.It fails when the difference was about 14 hours or so. Thanks Ok, so no driver / 32bit issues.
Error Im002 Odbc Driver Manager
It runs fine when executing job manually or when scheduled within a short period after a manual run. But not when there is a long period between the manual run and the scheduled run.
Microsoft Odbc Driver Manager Error
Do you have some more details: - Which SSIS version/edition are you using? - Which ODBC driver are you using (or what's the source)? - Which operating system are you using? - Does your package have some form of error logging with more details? Please mark the post as answered if it answers your question My SSIS Blog:.