Resolving Application Errors in Integration Manager on x64 Servers

 

Yesterday, while working with one of our new clients, we repeatedly received ‘ADO field is nothing’ errors when trying to preview data source data and  ‘DOC 1 ERROR: Unable to cast COM object of type’ error messages, while trying to run Integration Manager to bring in master files. The application would open correctly and we were able to do create new integrations, but we were unable to proceed.

 

While we couldn’t find anything in the Microsoft knowledgebase, I did come across this string on the Microsoft Communities website: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.greatplains&tid=3f69cb32-75c3-4938-bad5-796708e101df, which ultimately gave us our solution. Manano Gomez suggested two things to resolve these issues (evidently issues on both 32 bit and 64 bit machines: 1) install Service Pack 4 for Integration Manager and 2) re-register the MSscript.ocx file. Since this was a new installation, I was worried about applying a Service Pack on the fly, however I believe it was the re-reg that actually did the trick.

 

On 32 bit machines the MSscript.ocx file is found in the C:\Windows\System32\ directory. On 64 bit machines it’s found in the C:\Windows\SysWOW64\ directory. To re-register a component, go to Start à Run and in the run prompt type cmd. This will open the command prompt.

 

For 32 bit machines, type: regsvr32 C:\Windows\System32\MSScript.ocx

For 64 bit machines, type: regsvr32 C:\Windows\SysWOW64\MSScript.ocx

 

Successful registration of the .ocx file will result in a dialog as follows:

 

 

Should registration fail, you may need to re-install Integration Manager. Please contact your Microsoft Partner should you need assistance with Technical or Installation Support.