IAK_SHARED (0X8ABC8001) error -196735951 in DSC 8.6.1 runtime

[Lenvno]

I have installed a Labview DSC application on a machine with a fresh Windows installation. This installer has worked on other machines without issue. When the library deployment failed in the application,  I tried to create a process with the Disributed System Manager and got the above error.  The message said that the system was not set for MXS and that it may be caused by not re-booting after installing DSC.  Not the problem here.  I tried a repair of DSC runtime and found it failed because it could not stop the shared variable engine.  I tried several methods of stopping the service all failed except disabling it in Windows and re-booting.  It seems that something about the Windows installation is not correct.  I am doing this work remote from the target computer, so I am not sure of how the Windows XP pro was installed

[Lenvno]

Please note the corrected error number in the subject.  The original should have read error -1967357951.

[Robbob]

Lennvo,

When you say disable it in windows, do you mean you are stopping the service or use task manager to kill it?

I haven't seen this error before, but we may want to try an uninstall and reinstall of the DSC, repair doesn't seem to catch all issues.

[Lenvno]

Hello Rob,

I  used the services management window and set the property of the service to "disabled" then rebooted the computer.  I now believe that the reason none of the conventional methods can stop the service is that the service software is hung up. I have since tried a complete removal of software including DSC and Labview runtime.  It did not fix the problem, I cannot stop the shared variable engine. 

I have seen forum discussions about similar problems that involve conflict with device drivers that result in MAX database corruption.  I also tried the procedures recommended  to create a new database.  No luck.  I did this because it seems the NI service locator is not operating even though Windows shows it as AUtomatic and running.  The problem shows up as MAX unable to expand the software section of its tree.

Len

[Robbob]

Not sure if the MAX database corruption is part of the issue...but this seems related