NI-PAL service manager error

[jmass16]

Because of the autoranging issues that I am having, I need to update the DMM driver to 3.0.2.  I have tried the following, all ending in failure:

1. Install new driver (3.0.2 package) on top of old driver (3.0.1 package) - FAIL.
2. Remove ALL NI software using MsiBlast, install new driver package 3.0.2 - FAIL.
3. Remove ALL NI software using MsiBlast, this time, manually remove NI folders (left behind from the uninstall) within the "Program Files/National Instruments" folder.  This way to completely remove everthing - FAIL.
4. Install a fresh 3.0.1 package, now install 3.0.2 package - FAIL.
5. Install the 3.0.1 package.  Now, install the 3.0.2's NI MAX explorer (version 4.6.2) ONLY - FAIL.

The error is given below when I start NI-MAX.

I have absolutely no problems installing the 3.0.1 package.  Everthing works just like it's suppose to, it's the 3.0.2 package that I'm having problems with.  I believe it comes down to the 4.6.2 NI MAX explorer because first I can install the entire 3.0.1 package which installs the 4.6.0 NI MAX explorer.  Then when running the 3.0.2 install, I can choose to only install the NI MAX explorer 4.6.2 (without installing anything else).  It installs fine, but I still get the errors from above.  Since the 3.0.2 DMM driver requires the 4.6.2 NI MAX explorer, there's no way around not installing it with the DMM driver.

When I run the NI MAX explorer, this sequence of events is displayed on the NI MAX startup window:

1. "Initializing"
2. "Updating Device Configuration"
3. "Loading plug-ins"

The above error occurs during "Updating Device Configuration" (2.).  Any help would be much appreciated.

[mishkin]

The screenshots of the errors in MAX do not show up. Can you post them again?

[jmass16]

Sorry about that.  They should now be pictured below.

 

[mishkin]

It looks like the msvcr90.dll is pointed out as the faulty module. Normally during a corruption like this we would just want to reinstall the component responsible for the DLL. However in this case it is a Microsoft C Runtime Library. It is normally located here: C:\Program Files\National Instruments\RT Images\MSVS90\1.0

I am not entirely sure which component is responsible for installing the DLL, but one thing you can try is replacing that DLL with a new one. You can download it here (it's the same version as my msvcr90.dll)

Another thing you can try follow the steps for recovering from a MAX database corruption. 

[jmass16]

Thank you for your quick response!  I have tried recovering from a MAX database corruption and it too gave me the same error.  As for the msvcr90.dll file location, this folder (MSVS90) isn't in the suggested directory (or anywhere else when doing a search under the National Instruments directory).  I have attached a picture of the RT Images directory.

[mishkin]

If I understand correctly, you wiped all the NI software and reinstalled only certain components back. MSI Blast is actually not the best way of doing this, as it only runs certain uninstallers and doesn't remove registry keys, etc. I suggest you try the steps in the attached doc instead.

Certain directories on disk are probably missing because not all of the software was installed. Just as a heads up, the order of installation you want to follow is this: 

1. Labview

2. Modules and Toolkits

3. Drivers

Let me know how it goes. 

[jmass16]

Thank you very much mishkin for your help, but I'm afraid I still get the same error and I have followed your "Clean Reinstall Procedure.doc" document perfectly.  The msvcr90.dll version the MAX explorer is trying to use is located at "C:\Windows\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e".  I tried replacing this dll, thinking that maybe it got corrupted somehow, but that didn't work either.  What bothers me it that I can install the 3.0.1 DMM package just fine, it's the 3.0.2 package that I'm having trouble with.  Does anyone know what exactly is trying to use the msvcr90.dll?

[jmass16]

So, I removed the 9.0.30729.4148 version of the msvcr90.dll, and used the previous version, 9.0.21022.8.  This also caused the error, but at a different offset.

     msvcr90.dll: 9.0.30729.4148 - error at offset 0006ccb5

     msvcr90.dll: 9.0.21022.8       - error at offset ooo6c955

I used Dependency Walker to see if these offsets correspond to the same function, and they do,  _invalid_parameter_info(). 

[jmass16]

Here is a link to the definition of the function _invalid_parameter_info().

[Ali M]

Hello,

After following the clean uninstall procedure document, did you try installing DMM driver to 3.0.2 alone (instead of 3.0.1 then 3.0.2)? Additionally, what operating system are you performing this installation?

Regards,

Ali M

Applications Engineer

National Instruments