285
Hi everyone,
Title pretty much explains it. We are getting the following error in Integration Manager: ERROR [IM002] [Microsoft] [ODBC Driver Manager] Data Source name not found and no default and no default driver specified.
I have ran everything as administrator. I have checked the odbc. It is 32 bit and testeing worked. I am able to log into GP. Not sure what's going on.
Make a backup of IM...mdb. Double click the original xxx.mdb file. May get a message "Database is in inconsistent state, trying to repair..." . Once Access is done repairing the database the Integration Manager should function as normal. I'm guessing either Windows patching or Office service pack corrupted IM database.
Hey everyone,
So I have a good update. I tried uninstalling again, etc. but was having no luck when running as admin. I was able to open the Convert Database window so I made a backup of the IMD file and tried converting it. It failed. I got the error "Database creation error - Database creation error - Unrecognized database format '(file location)'.
I then went into the ODBC Data Source Administer and the System DSN tab. I added the Microsoft Access Driver, selected the IMD file, clicked Repair, and it successfully repaired the file. I was able to open Integration Manager without error. I then tested and was able to open all of the windows where I was getting the message earlier. I also tested the Convert Database process again and it worked without problem. I reached out to the client to have them test their integrations, but I think this may be resolved.
Thank you all for your suggestions and input. I truly appreciate it!
Hello RJarell,
Richards' recommendation of Running as Admin is what I have seen resolve the issue quite a few times.
Rarely, I have seen an issue crop up with the Access database, which is usually resolved by running through a compact and repair:
support.microsoft.com/.../compact-and-repair-a-database-6ee60f16-aed0-40ac-bf22-85fa9f4005b2
As a note, if you set both GP and IM to run as an Admin on their Properties, you can use GP to launch IM using the "Run Integration" menu without running into any of the "Needs Admin rights" issues. This is how I run IM and GP unless I am testing something specific:
To resolve this problem, start Integration Manager by Right-Clicking on the Integration Manager shortcut and choose "Run as administrator". This will start Integration Manager using the Administrator access token so the application will have sufficient rights to create the directory structure mentioned in the error message and write the default configuration file. If this does not work trying uninstalling and then remove all traces of IM using something like Revo and then reinstall. There are files kept in a common Microsoft folder. I bet some of these files are corrupt. Make sure the IM.cnk in this folder gets removed. C:\Program Files (x86)\Common Files\Integration Manager 18
Hey all,
To give a small update. The options points to the shared file. It is not mapped to a drive letter and is pointed to the SQL Server Name. I verified that name did not change. I can still browse to the IM database file through integration manager.
Bill, there isn't much to post when it comes to the Object Browser window. I click it, the error pops up, I click ok, the error message closes, and nothing pops up. The IM file is set to allow all domain users to see and modify it.
For more info on the DSN, it is under C/Windows/SysWOW65. It is set up under System DSN. There is only 1 option there so I am assuming it is the correct one. It is what GP is using. I tested the connection and it is working.
I tried repairing IM, and then uninstalling and re-installing. Same error.
Richard, that total would make sense - maybe a drive mapping has changed - maybe the security for the user accessing the network drive.
I would also suggest you click on Options and then see where IM is pointing for its integrations. Sounds like it is having trouble reading the IM.MDB or IM.IMD file. I bet someone has pointed it to the wrong file.
Can you open the window as suggested by Richard and post a clip of the screen so the community can see what you are seeing. It is hard to understand how the entire DSN has 'vanished'
With some added details I think the community might be in a better position to assist.
You might want to challenge the IT on the comment that nothing has changed in the domain - ask them directly if there were any updates or patches done on the Server or servers that come from Microsoft. Over the past few months we have seen that updates to security in one section of the Microsoft stack has an impact in another part of the stack - so - I would check with them.
I would also like to add that this is happening on the terminal server as well (the only other computer with GP at the moment). It happened suddenly. It was working last week and then Friday gave this error. We spoke to their IT who has said no changes have been made to the domain, etc.
#1
André Arnaud de Cal...
291,711
Super User 2024 Season 2
#2
Martin Dráb
230,458
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
