So like most of you, I got an e-mail from ESRI saying the new ArcMap 10.2 was released with a lot of fixes. Never really had just a huge problem with 10/10.1 besides a few random glitches but I like to stay current so I downloaded the new version. Get to install 10.2 on top of 10.1 without the whole uninstall prior version - check. Worked fine. Updated the License Manager - caught a few snags there due to running the "License Server" on the same workstation that I run ArcMap on and how our network is setup but got thru that and was good to go. Or so I thought.
First time loading up 10.2 it froze on me so I had to Ctrl+Alt+Del and end the process. After that when I would try to open the program I kept getting some kind of .NET Framework error but that would disappear too quickly to actually read and the program would shut down. Reboot the computer - still doesn't work. Reinstalled .NET Framework 3.5 - still doesn't work. Completely uninstalled every version of .NET Framework and only installed the 3.5 version from ESRI's website - still doesn't work. Same .NET Framework error that I can't mange to read before it disappears. Finally get fed up and uninstalled ArcMap 10.2 and did a fresh install. Boom. Got ArcMap 10.2 working!
That's the good news. ArcMap 10.2 works. BUT! Here is my problem (and work around - not so much a fix) - I also use an appraisal software on this same workstation that I have to use as a part of my job. After installing ArcMap 10.2 the appraisal software starts acting up. Try to print from the appraisal software would result in an error saying "[Microsoft][ODBC Service Manager] No default driver specified and no file name" or something similar to that. As well as when I actually tried to work in the appraisal software - I would have to reconfirm what database it should be using after every single change. Very annoying. I'm thinking I messed something up by uninstalling/reinstalling all those .NET Frameworks so I try uninstalling/reinstalling the appraisal software. Doesn't work. I spend an entire day rebooting/uninstalling/reinstalling and playing with different configurations of the appraisal software and the .NET Framework but nothing works. Finally I swallow my pride and call for help with the people who provide my office with our appraisal software and they know exactly what is going on as several of their clients have called with this same issue.
ArcCatalog 10.2 is the culprit.
That's right. For some reason ArcCatalog 10.2 is interferring with my SQL Server connection for a completely seperate program.
So I was advised by our appraisal software provider to uninstall just the ArcCatalog part of ArcGIS - of course its not that simple for me and I end up having to completely uninstall the entire ArcMap 10.2 then do a custom install leaving out the ArcCatalog. Guess what. Everything works now. Of course - as I said above - this is just a "work around" as you no longer have ArcCatalog and that can be a fairly useful tool when needed. Not a fix - I know but personally I rarely need the ArcCatalog so for now atleast I can get back to work. Hope this information helps any others with similar problems and that ESRI can fix their ArcCatalog from interferring with other programs connections to a SQL Server database.
FYI - my workstation is still running a 32-bit version of Windows XP while our server is 64-bit. Don't know if that makes any difference here but while trying to Google a fix on the [ODBC Service Manager] issue that seemed to be a common thread.
First time loading up 10.2 it froze on me so I had to Ctrl+Alt+Del and end the process. After that when I would try to open the program I kept getting some kind of .NET Framework error but that would disappear too quickly to actually read and the program would shut down. Reboot the computer - still doesn't work. Reinstalled .NET Framework 3.5 - still doesn't work. Completely uninstalled every version of .NET Framework and only installed the 3.5 version from ESRI's website - still doesn't work. Same .NET Framework error that I can't mange to read before it disappears. Finally get fed up and uninstalled ArcMap 10.2 and did a fresh install. Boom. Got ArcMap 10.2 working!
That's the good news. ArcMap 10.2 works. BUT! Here is my problem (and work around - not so much a fix) - I also use an appraisal software on this same workstation that I have to use as a part of my job. After installing ArcMap 10.2 the appraisal software starts acting up. Try to print from the appraisal software would result in an error saying "[Microsoft][ODBC Service Manager] No default driver specified and no file name" or something similar to that. As well as when I actually tried to work in the appraisal software - I would have to reconfirm what database it should be using after every single change. Very annoying. I'm thinking I messed something up by uninstalling/reinstalling all those .NET Frameworks so I try uninstalling/reinstalling the appraisal software. Doesn't work. I spend an entire day rebooting/uninstalling/reinstalling and playing with different configurations of the appraisal software and the .NET Framework but nothing works. Finally I swallow my pride and call for help with the people who provide my office with our appraisal software and they know exactly what is going on as several of their clients have called with this same issue.
ArcCatalog 10.2 is the culprit.
That's right. For some reason ArcCatalog 10.2 is interferring with my SQL Server connection for a completely seperate program.
So I was advised by our appraisal software provider to uninstall just the ArcCatalog part of ArcGIS - of course its not that simple for me and I end up having to completely uninstall the entire ArcMap 10.2 then do a custom install leaving out the ArcCatalog. Guess what. Everything works now. Of course - as I said above - this is just a "work around" as you no longer have ArcCatalog and that can be a fairly useful tool when needed. Not a fix - I know but personally I rarely need the ArcCatalog so for now atleast I can get back to work. Hope this information helps any others with similar problems and that ESRI can fix their ArcCatalog from interferring with other programs connections to a SQL Server database.
FYI - my workstation is still running a 32-bit version of Windows XP while our server is 64-bit. Don't know if that makes any difference here but while trying to Google a fix on the [ODBC Service Manager] issue that seemed to be a common thread.