Troubleshooting Connection Manager
This chapter offers solutions to common installation, configuration, and instrument communication problems, as well as instruction on using the server diagnostics tool.
Server Installation and Configuration
This section lists common Connection Manager server installation and configuration problems and their possible solutions.
Server IO Fails Running Under the LocalSystem Account
When running the Connection Manager as a Windows service (see Running the Server as a Windows Service) and trying to connect to the CM ESG E4438C Sink (or other CM component), the following error message (or a message announcing the VISA32.dll did not load) is displayed.
Solution: use a named account.
Run the Connection Manager Server under an account with Administrator privileges.
The problem is a conflict involving the SICL interface and Connection Manager interface on certain PCs. In some cases, Connection Manager cannot be run as a LocalSystem account service.
To check if Connection Manager is running under a LocalSystem Account:
- From the Windows toolbar, click Start > Settings > Control Panel.
- In the Control Panel dialog, click Administrative Tools.
- In the Administrative Tools dialog, click Services. (If you do not have access to the Services icon from the Administrative Tools dialog, see following section.)
- In the Services dialog, right-click on the Agilent Connection Manager and select Properties.
- In the Properties dialog, select the Log On tab.
- Observe the Log on as: setting.
If your PC is set to LocalSystem account, follow the instructions in Configuring User Account Privileges on the PC.
If you do not have access to the Services icon from the Administrative Tools dialog
Some PCs may not have the Services shortcut available in the Administrative Tools dialog. If so, follow these steps.
- In Windows Explorer, navigate to %SystemRoot%\system32 to find the services.msc (Microsoft Common Console Document). For example, C:\WINNT\system32\services.msc.
- Double-click on the services.msc file to bring up the Services dialog.
- In the Services dialog, right-click on the Agilent Connection Manager and select Properties.
- In the Properties dialog, select the Log On tab.
- Observe the Log on as: setting.
If your PC is set to LocalSystem account, follow the instructions in Configuring User Account Privileges on the PC.
No Connection and "Connection Refused" Error Messages
Solution: for systems with firewalls, specify the server port number to allow access.
Firewall software, like Norton Internet Security, Zone Alarm, or the Windows XP Personal Firewall application, can interfere with the server's ability to communicate on a network. This will manifest itself as the client application receiving a Connection Refused message when trying to run a measurement.
Most of these applications allow you to configure the server to allow certain applications to access the network. For firewall software applications that require the port number for the CM server, see the C:\Program Files\Agilent\Connection Manager Server\MsmtSrvr.exe.config file for the configured port number the server uses to communicate with clients.
The server uses transient ports, which allow for faster data transfer. The ports are allocated dynamically, starting with port number 5001,extending to 10,000.
Solution: determine if another process is binding the port and reconfigure.
The server allows network communication from clients by listening to a port identified in the MsmtSrvr.exe.config file. If the server cannot bind the port, possibly because another application is using that port, the client will get " connection refused " messages.
In addition, the server machine will run slowly. The server will try to restart itself in the event that it exits abnormally. Failure to bind to the port in the MsmtSrvr.exe.config file will cause an abnormal exit. Continued failure to bind the port will cause the server to continually try to restart, resulting in a slow server PC.
You can determine if there is a port conflict by running the command " netstat -a " from a command prompt on the server PC.
If the client receives a message that the connection has been refused and the server becomes very slow, it is probable that the server port is being used by another process.
To verify this problem, complete the following steps:
- From the Windows tool bar, select Start > Settings > Control Panel > Administrative Tools > Services __ to open the Services window.
- Highlight Agilent Connection Manager.
- Select Action > Stop to stop the Connection Manager service.
- Open a Command Prompt window and type:
netstat -a - Press Enter.
This provides a list of active connections on the server workstation. If the port number used by Connection Manager is present in the Active Connections list, another process is using the Connection Manager port.
If this is the case, you must either stop this process to free the port or select a new port for use by Connection Manager. To change the server's port number, refer to The MsmtSrvr.exe Process.
To solve this problem, stop the server using the Windows Services control panel applet, change the server's port entry in the MsmtSrvr.exe.config file, and restart the server.
Since the clients and server must agree on this port number, change the client parameters to use the port value you just put into the MsmtSrvr.exe.config file.
 | Note The Process Explorer tool available from SysInternals, http://www.sysinternals.com/, can help to determine if the cause of refused connections is due to abnormal server termination. If you see the server process (MsmtSrvr.exe) highlighted in red, it (the server) is continuously re-spawning. |
Measurements Using Plug and Play Drivers Fail
Solution: install the required the required driver(s).
Several measurements depend on having Plug and Play drivers installed on the server PC. If a required driver is not available, the client displays an error dialog, as shown.
To correct this, you must install the driver on the server PC. Drivers are available at the Drivers and Downloads link at the Agilent Developer Network web site:
[www.agilent.com/find/adn]
Solution: install the Agilent IO libraries with Agilent VISA set to Primary.
Some of the Connection Manager measurements achieve instrument control by using Plug and Play drivers. Those drivers depend on an Application Programming Interface known as VISA to communicate with instruments. There are two major vendors supplying VISA implementations. Those implementations are not necessarily compatible, so, when installing the Agilent IO Libraries, you may be presented with the need to choose between installing Agilent VISA as either Primary or Secondary. Always install the Agilent VISA Libraries as Primary. For a complete description of this topic, refer to the Agilent IO Libraries and NI Software document found at:
http://www.agilent.com/find/iolib.
You can determine if your IO libraries have VISA installed and if VISA is installed as Primary by selecting the About Agilent IO Libraries Control entry from context menu in the IO libraries icon in the task bar.
To install the IO libraries with VISA as primary, run the IO libraries installation on the PC server, select the custom installation button, then select the option that does a full installation with VISA as primary.
Part of the process of installing a Plug and Play driver causes the driver to record where it finds its VISA library. If you upgrade or otherwise replace the IO Libraries installation and change the installation from primary to secondary ( or vice versa), the Plug and Play driver may not be able to find its VISA implementation. This results in a measurement displaying an error dialog indicating that the T&M Toolkit's driver interoperation layer encountered a failure trying to call the driver's Init function.
The solution is to uninstall the IO libraries and reinstall with VISA as primary. Then uninstall and reinstall the Plug and Play driver. Drivers are available at the Drivers and Downloads link at the Agilent Developer Network web site:
[www.agilent.com/find/adn]
For support installing and configuring the Agilent IO Libraries and for answers to your hardware or measurement questions, contact your local Agilent Instrument Support Center at the number found on the following website:
[www.agilent.com/find/support]
Server Unregisters After Installing 2003C then Uninstalling 2003A
Solution: restart the measurement server from the control panel applet.
Part of the uninstalling process unregisters the Connection Manager Server - a Windows service. Since this is a system component, only one instance may be actively registered on a system. When installing the server, the system registry gets updated to use the server in whichever version of ADS is being installed. Likewise, uninstalling deletes the registry entries related to the server.
If you install 2003A, then install 2003C, the registry uses the 2003C server. If you subsequently remove 2003A, the server registry entries will be removed, and the server will no longer be configured.
To configure the server, open a command window on the server workstation and perform the following procedure:
- From the <ADS Installation Directory Path>/bin directory, enter MsmtSrvc -install .
- Open the Services control panel applet and select the Agilent Connection Manager entry's properties.
- Select the login account you wish the server use.
- Select the server startup option.
- Start the service running by choosing Start from the control panel applet.
Missing Blue IO icon in System Icon Tray
Solution: uninstall ADS 2003C server and install ADS 2004A server.
The blue IO icon must be active in the Windows system icon tray for the Connection Manager server to run.
The IO Libraries installation places a shortcut to the IO Libraries application called iprocsvr in the system program startup group. Iprocsvr is the entity responsible for putting the IO icon in the system icon tray. If iprocsvr is not running on the server PC, instrument IO will not function.
The IO Libraries will not operate when there is no interactive logon session running on the CM server workstation. This prevents the CM server from performing instrument IO unless a user is interactively logged onto the server PC.
ADS 2003C and Earlier Running Server as Windows Service
As a work around, the ADS 2003C CM Server installation removed the iprocsvr shortcut. At startup, the ADS 2003C server would check to see if iprocsvr was running. If not, the ADS 2003C server would start iprocsvr.
Running the 2003C server uninstall will restore the iprocsvr shortcut to the system program startup group.
ADS 2004A Running Server as Windows Application
To integrate better with the IO Libraries, the 2004A CM server runs as a Windows application. The 2004A server installation unconfigures any previous server, effectively replacing the Windows service with a Windows application. This is necessary, because two servers cannot run and listen to the same network port simultaneously.
If you install the 2004A server without first running the 2003C server uninstall, the iprocsvr shortcut may not be in the system program startup group.There will be no IO icon in the system tray and any attempt to perform instrument IO will fail.
To prevent this, run setup.exe from the /CM_Server directory of disk 2 in the 2003C media kit and select the option to uninstall.
Alternatively, you could create a shortcut to the iprocsvr.exe program in the system program startup group.
Solution: enable process listing.
In ADS 2003C, the CM server process ( MsmtSrvr.exe ) would try to start the IO Libraries' IO Control application ( iprocsvr.exe - the program responsible for putting the blue IO icon in the icon tray) if that application was not already running.
To know whether it is necessary to start the IO Control application, the CM Server program would list the processes currently running on the server PC. Some Windows installations disable the ability to perform this process listing, so the CM Server could not run.
This results in the CM client not connecting, even after having changed the Windows service to run under an account other than LocalSystem. Also, the Diagnostics application would not create an output file.
To verify that the problem is related to the server PC having disabled the ability to list processes, follow these steps.
- In Windows, click Start > Settings > Control Panel.
- From the Control Panel dialog, click Administrative Tools > Event Viewer.
- Scroll down to find error entries titled AgilentConnectionManager.
- Right-click on the error entry and select Properties.
- In the Description field, observe the following description.
Event Type: Error Event Source: AgilentConnectionManager Event Category: None Event ID: 4 Date: 6/15/2004 Time: 12:24:54 PM User: N/A Computer: SANC040320844 Description: The following information is part of the event: Caught exception: System.InvalidOperationException: Process performance counter is disabled, so the requested operation cannot be performed. at System.Diagnostics.NtProcessManager.GetProcessInfos\(PerformanceCounterLib library\) at System.Diagnostics.NtProcessManager.GetProcessInfos\(String machineName, Boolean isRemoteMachine\) at System.Diagnostics.ProcessManager.GetProcessInfos\(String machineName\) at System.Diagnostics.Process.GetProcessesByName\(String processName, String machineName\) at System.Diagnostics.Process.GetProcessesByName\(String processName\) at Agilent.MeasurementServer.MsmtSrvr.StartSiclDaemons\(Boolean& weStartedSicl, Process& iproc\) at Agilent.MeasurementServer.MsmtSrvr.Main\(String\[\] args\).
This verifies that the process performance counter has been disable, in turn disabling Connection Manager.
To enable the process performance counter (and thereby Connection Manager), from an account with Administrator privileges, complete the following steps.
- Open a command prompt and cd to the ADS installation's bin directory, for example, cd c:\ads2003c\bin
- Stop the CM service by executing the command MsmtSrvc -stop .
- Open the Registry Editor by entering regedit .
- Open the registry key HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\PerfProc\Performance.
- If that registry key contains a value named Disable Performance Counters, set its value to 0 , as shown below.
- Restart the CM Service by executing the command MsmtSrvc -start.
No Instrument Access when Using Agilent 89600 Software
Solution: unconfigure the instrument using the Agilent 89600 Select Hardware dialog.
Agilent 89600 software claims total ownership of instruments for the length of time those instruments are configured.
If Connection Manager generates and error when trying to communicate with an instrument that has been used with the Agilent 89600 software, unconfigure the instrument using the Agilent 89600 Select Hardware dialog.
To unconfigure the instruments, follow these steps.
- Open the 89600 software.
- From the Main dialog, choose Utilities > Hardware.
- Using the instrument tabs, uncheck instruments you want to use with Connection Manager.
Instrument Interface and Communication
This section list common instrument interface and communication problems and their possible solutions.
The Server Hangs During Measurements or Remote Instrument Explorer is not Responding
Solution: observe the instrument display, correct any error state, and clear any instrument errors.
Many older instruments may generate error messages and shut down their IO when they encounter an invalid state setting or command. This will disrupt instrument communication until the error state has been corrected and the error message has been cleared from the queue. Correct any invalid settings, ensure the instrument is receiving the correct commands, clear the error queue, and repeat the measurement.
Solution: connect and power on all instruments listed in the IO configuration.
If you have configured a LAN-connected instrument, but the instrument is not connected or not powered on, the IO Libraries will try to open every listed device. Since the default time out value for opening a LAN instrument is 2 minutes, any absent LAN-connected instrument could cause the IO Libraries to take a long time to open an instrument session. If an instrument listed in the server workstation IO configuration is not accessible (i.e., disconnected or turned off), the client's Remote Instrument Explorer will become unresponsive.
To run the IO Config setup
To check for an unresponsive instrument, follow these steps.
- In the server's Windows system tray, select IO > Run IO Config.
- In the IO Config dialog, highlight the TCPIP lan entry in the Configured Interfaces group box and select Edit.
- In the LAN Client dialog, select Edit VISA Config.
- The TCPIP dialog lists which instruments are connected to the server through the LAN.
- Ensure that the instruments are connected and functioning properly.
- If an instrument is not functioning, you must either return it to a functional state or remove it from the IO config and restart the Connection Manager service.
Run VISA Assistant to Verify Communication Link
To verify the server recognized your GPIB instrument, follow these steps.
- In the server's Windows system tray, select IO > Run VISA Assistant.
- Observe your instrument displayed in the VISA Assistant display panel.
- Close VISA Assistant.
Communication Problems with Older Instruments
Solution: send commands through the LAN server to slow the rate.
Late model computers can send instructions faster than many vintage instruments can process them. This situation often manifests itself when the instrument returns a message that is not consistent with the measurement being made.
It is possible to slow down communications with an older instrument by running the interface through the IO Libraries LAN server, causing the instructions to be sent to the instrument at a slightly slower rate.
To send commands through the IO server, complete the following steps.
- Run siclland.exe , located in the IO Libraries installation bin directory (i.e., \ Program Files \ Agilent \ IO Libraries \ bin ) on the server workstation.
- Run IO Config and add a VISA LAN client entry.
- Select Configure and specify the IP address of the server workstation (i.e., the workstation running IO Config ).
- When you use the Connection Manager client to specify an instrument, select the instruments shown on the LAN interface ( GPIB1 in the preceding example).
Solution: Extend the length of the GPIB cabling between the server and the instrument.
Extending the length of GPIB cable between the server and the instrument can decrease the speed at which the instrument receives data from the server.
Connection Manager Server Diagnostics
The Connection Manager client and server dialogs include server diagnostics. The Connection Manager Server Diagnostics and Diagnostics Display dialogs collect and display server configuration information for use in troubleshooting instrument communication problems.
| Note At no time does the server implementation of this capability interact directly with instruments. Doing so could interrupt a measurement in progress. |
As shown, the client dialog contains a Server entry field, an information display area, as well as OK , Refresh , Save to file... , and Help buttons. The server dialog contains a an information display area, as well as OK and Save... buttons.
The Server field displays the name of the currently configured server.
The display area will contain the information gathered by the diagnostics routine. For individual explanations, see Understanding the Server Diagnostics Output.
Choose OK to dismiss the dialog.
Choose Refresh to refresh the diagnostic information after making changes to your server configuration.
Choose Save to file... or Save... to open a Save File dialog where you can save the diagnostic dialog contents in a text file. E-mail this text file to Agilent EEsof support staff to provide them with the information to diagnose an instrument IO problem.
To Diagnose the Server From the Server Window
- From the Connection Manager Server main window, choose Diagnostics > Run Diagnostics.
- Observe the information in the display area.
- Make necessary corrections to the server configuration.
- Close the server.
- Reopen the server.
- Choose Diagnostics > Run Diagnostics.
- Observe the information in the display area.
- To save the diagnostics information, click Save to file... and enter a file name and directory path.
- To exit diagnostics, click OK.
To Diagnose the Server From the Client Window
- From the Connection Manager Client main window, choose Help > Diagnostics.
- Choose server using the Set Server dialog and click OK.
- Observe the information in the display area.
- Make necessary corrections to the server configuration.
- Click Refresh to run the diagnostics again.
- To save the diagnostics information, click Save to file... and enter a file name and directory path.
- To exit diagnostics, click OK.
Understanding the Server Diagnostics Output
This section describes the individual server diagnostics output items, from top to bottom of the display.
The CM Service Information
This section contains server version, server installation path, and the operating state of the server, as shown:
CM Service version info: 3.0.2004.1, Installation path: C:\Program Files\Agilent\Connection Manager Server\MsmtSrvc.exe, Service state: The service is running.
Server version 2.0.2003.3 is ADS 2003C, server version 3.0.2004.1 is ADS 2004A, server version 4.0.2005.1 is ADS 2005A, ADS 2006A is 5.0.2006.1.
The installation path is read from the registry key HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\AgilentConnectionManager\ImagePath. The installation package creates this registry key when you install the Connection Manager server.
The diagnostic routine queries the Service Control Manager to obtain the service state to determine whether you are running the CM server as an application or a Windows service.
In server versions prior to version 3.0.2004.1, the CM server functioned as a Windows service. Versions 3.0.2004.1 and later function as a Windows application. The 2004A CM server installation, by default, will stop a previous instance of the Windows service, remove the service from the system, then configure the Windows application to take its place.
If preferred, you can override this new default and continue to use the Windows service. Even though the Windows service is not configured into the system, it is still installed with ADS 2004A.
If the service is not running, the following message appears on the display:
CM Service version info: 3.0.2004.1, Installation path: C:\Program Files\Agilent\Connection Manager
Server\MsmtSrvc.exe
Could not get service status. System error recorded: The service has not been started.
If the service isn't installed, the following message appears on the display:
Could not read service registry key. System error recorded:
IO Libraries Information
This section records the IO Libraries registry information. This is a complete description of all IO configuration settings. This section contains IO libraries installation path, version, and configured interfaces, as shown (important entries are highlighted):
IO Libraries set up correctly
IO Libraries version: M.01.01.04, Installation directory: C:\Program Files\Agilent\IO Libraries
Agilent Visa is primary: True
IO Libraries registry information...
Registry key: CurrentVersion
Registry name: Platform, Registry value: -1
Registry name: PlatformName, Registry value: unknown
Registry name: BaseDir, Registry value: C:\Program Files\Agilent\IO Libraries
Registry name: CurrentVersion, Registry value: M.01.01.04
Registry name: CurrentVersionNumber, Registry value: 1291911428
Registry name: ProductCode, Registry value: \{04107B50-CCF1-11D3-931C-00108301D203\}
Registry name: InstallLevel, Registry value: 256
Registry name: 1394VersionCheck, Registry value: 5.0.2195.2096
Registry name: IOLibrariesVisaPresent, Registry value: 1
Registry name: IOCFGRebootVal, Registry value: 0
Registry name: IOControlHidden, Registry value: 0
Registry key: Aliases
Registry name: Serial, Registry value: ag232i
Registry name: ag82341, Registry value: ag341i
Registry name: hp82341, Registry value: ag341i
Registry name: hp82340, Registry value: ag341i
Registry name: e2071a, Registry value: ag341i
Registry name: 82340, Registry value: ag341i
Registry name: 82341, Registry value: ag341i
Registry name: ag82350, Registry value: ag350i
Registry name: hp82350, Registry value: ag350i
Registry name: 82350, Registry value: ag350i
Registry name: e2078a, Registry value: ag350i
Registry name: hpe8491, Registry value: ag491i
Registry name: age8491, Registry value: ag491i
Registry name: e8491, Registry value: ag491i
Registry name: hpilan, Registry value: agtlan
Registry name: hptcpi, Registry value: agtlan
Registry name: agilan, Registry value: agtlan
Registry name: agtcpi, Registry value: agtlan
Registry name: usb488, Registry value: agUsb488
Registry name: 82357, Registry value: ag357i
Registry key: INTF1
Registry name: Name, Registry value: gpib0
Registry name: VISAName, Registry value: GPIB0
Registry name: VISAIntfType, Registry value: GPIB
Registry name: VISAAutoConfigDriver, Registry value: AUTOCF
Registry name: VISAAutoConfig, Registry value: System.Byte[ ]
Registry name: LU, Registry value: 8
Registry name: Interface, Registry value: 82357
Registry name: BusAddr, Registry value: 21
Registry name: SysCtl, Registry value: 1
Registry name: Slot, Registry value: 0
Registry name: TimeoutFloorMsec, Registry value: 2000
Registry name: TimeoutUsbFlushMsec, Registry value: 2000
Registry name: TimeoutWrCompleteFlushMsec, Registry value: 15000
Registry name: IOBufferSizeKb, Registry value: 64
Registry name: PNPvid, Registry value: 0x00000957
Registry name: PNPmodel, Registry value: 0x00000107
Registry name: PNPsn, Registry value: US42251605
Registry name: EnableExport, Registry value: System.Byte[ ]
Registry key: VISADev
Registry key: VISAIntfRsrc
Registry key: GPIB0::INTFC
Registry name: Driver, Registry value: INSTR
Registry name: Prefix, Registry value: INTFC
Registry key: INTF3
Registry name: Name, Registry value: lan
Registry name: LU, Registry value: 30
Registry name: Interface, Registry value: agtlan
Registry name: VISAName, Registry value: TCPIP0
Registry name: VISAIntfType, Registry value: TCPIP
Registry name: VISAAutoConfigDriver, Registry value: AUTOCF
Registry name: VISAAutoConfig, Registry value: System.Byte[ ]
Registry name: log_errors, Registry value: 1
Registry name: lan_delta, Registry value: 25
Registry name: sicl_infinity, Registry value: 120
Registry name: lanProtocol, Registry value: 1
Registry name: Slot, Registry value: 0
Registry name: BusAddr, Registry value: 0
Registry name: sigio, Registry value: 0
Registry name: EnableExport, Registry value: System.Byte[ ]
Registry key: VISADev
Registry key: TCPIP0::123.456.789.101::inst0
Registry key: TCPIP0::123.456.789.101::inst0::INSTR
Registry name: Driver, Registry value: INSTR
Registry name: Prefix, Registry value: INSTR
Registry key: VISAIntfRsrc
Registry key: INTF4
Registry name: Name, Registry value: usb0
Registry name: VISAName, Registry value: USB0
Registry name: VISAIntfType, Registry value: USB
Registry name: VISAAutoConfigDriver, Registry value: AUTOCF
Registry name: VISAAutoConfig, Registry value: System.Byte[ ]
Registry name: LU, Registry value: 20
Registry name: Interface, Registry value: usb488
Registry name: EnableExport, Registry value: System.Byte[ ]
Registry key: Usb488Devices
Registry key: VISADev
Registry key: VISAIntfRsrc
Registry key: PARAMS
Registry name: ag232i, Registry value: LU,Name,Interface,NotUsed,PortNumber,SRQ,
HWFlowControl
Registry name: ag341i, Registry value: LU,Name,Interface,Slot,BusAddr,Switches,SysCtl,IRQ,
PNPvid,PNPsn
Registry name: ag350i, Registry value: LU,Name,Interface,Slot,BusAddr,PNPvid,PNPModel,
PNPsecId,PNPsn,SysCtl,PNPprefix
Registry name: ag491i, Registry value: LU,Name,Interface,NotUsed,NotUsed,CageIdHi,CageIdLo,
RsrcMngrDelay,VmeBto,VmeBusReqLvl,ExtClockEnable,ExtTrigOutPolarity,ExtTrigInLevel,ExtTrigInPolarity,
UseAllExtendedMem
Registry name: agtlan, Registry value: LU,Name,Interface,Slot,BusAddr,sicl_infinity,
lan_delta,sigio,log_errors,reserved,lanProtocol
Registry name: aglansvr, Registry value: LU,Name,Interface,Slot,BusAddr,sicl_infinity,
log_errors,log_locks_conns,keepalives
Registry name: agUsb488, Registry value: LU,Name,Interface,Slot,BusAddr
Registry name: ag357i, Registry value: LU,Name,Interface,Slot,BusAddr,PNPvid,PNPmodel,PNPsn
Registry key: VISAInfo
Registry name: , Registry value: Comment: General Information on Agilent's VISA Implementation
Registry name: Spec Version, Registry value: 3145728
Registry name: Manufacturer, Registry value: Agilent Technologies
Registry name: Copyright, Registry value: Copyright Agilent Technologies, 2003.
Registry name: ManfVersion, Registry value: M.01.01.04
Registry name: LastMod, Registry value: Fri Apr 30 10:34:17 2004
Registry name: ModTool, Registry value: Agilent VISA Configuration Tool
Registry name: ManfVersionNbr, Registry value: 1291911428
Registry name: ManfID, Registry value: 4095
Registry name: Logging, Registry value: OFF
Registry name: MaxSessNbr, Registry value: 256
Registry name: MaxNbrOfProcs, Registry value: 64
Registry name: DefaultQSize, Registry value: 50
Registry name: SleepMs, Registry value: 0
Registry name: DefaultLockWait, Registry value: 0
Registry name: DefaultAllowLocalSpaceFifo, Registry value: 0
Registry key: DefaultIntfRsrcs
Registry name: , Registry value: Interface Resources to load during configuration ADD
functions
Registry key: BACKPLANE
Registry name: DrvrName, Registry value: INSTR
Registry name: PrefixName, Registry value: BACKPLANE
Registry name: GPIB, Registry value: System.Byte[ ]
Registry name: VXI, Registry value: System.Byte[ ]
Registry name: GPIB-VXI, Registry value: System.Byte[ ]
Registry name: ASRL, Registry value: System.Byte[ ]
Registry name: TCPIP, Registry value: System.Byte[ ]
Registry name: USB, Registry value: System.Byte[ ]
Registry key: INTFC
Registry name: DrvrName, Registry value: INSTR
Registry name: PrefixName, Registry value: INTFC
Registry name: GPIB, Registry value: System.Byte[ ]
Registry name: VXI, Registry value: System.Byte[ ]
Registry name: GPIB-VXI, Registry value: System.Byte[ ]
Registry name: ASRL, Registry value: System.Byte[ ]
Registry name: TCPIP, Registry value: System.Byte[ ]
Registry name: USB, Registry value: System.Byte[ ]
Registry key: MEMACC
Registry name: DrvrName, Registry value: INSTR
Registry name: PrefixName, Registry value: MEMACC
Registry name: GPIB, Registry value: System.Byte[ ]
Registry name: VXI, Registry value: System.Byte[ ]
Registry name: GPIB-VXI, Registry value: System.Byte[ ]
Registry name: ASRL, Registry value: System.Byte[ ]
Registry name: TCPIP, Registry value: System.Byte[ ]
Registry name: USB, Registry value: System.Byte[ ]
Registry key: DefaultRsrcs
Registry name: , Registry value: Resources to load during auto-connect and configuration
ADD functions
Registry key: INSTR
Registry name: DrvrName, Registry value: INSTR
Registry name: PrefixName, Registry value: INSTR
Registry name: GPIB, Registry value: System.Byte[ ]
Registry name: VXI, Registry value: System.Byte[ ]
Registry name: GPIB-VXI, Registry value: System.Byte[ ]
Registry name: ASRL, Registry value: System.Byte[ ]
Registry name: TCPIP, Registry value: System.Byte[ ]
Registry name: USB, Registry value: System.Byte[ ]
Registry key: SOCKET
Registry name: DrvrName, Registry value: INSTR
Registry name: PrefixName, Registry value: SOCKET
Registry name: GPIB, Registry value: System.Byte[ ]
Registry name: VXI, Registry value: System.Byte[ ]
Registry name: GPIB-VXI, Registry value: System.Byte[ ]
Registry name: ASRL, Registry value: System.Byte[ ]
Registry name: TCPIP, Registry value: System.Byte[ ]
Registry name: USB, Registry value: System.Byte[ ]
The diagnostics routine reads this information out of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Agilent\IO Libraries\CurrentVersion.
Agilent IO Libraries version M.01.01.04 is included with ADS 2004A and ADS 2003C.
To return the configured interfaces information, the routine dynamically loads the visa32.dll library and queries the interface. To return the local interfaces information, the routine loads the sicl32.dll library and queries the logical unit information.
For Plug and Play drivers to work correctly, VISA must be installed and the Agilent VISA library has to be configured as Primary.
With regards to the entry Registry key: TCPIP0::123.456.789.101::inst0, when you add a device to the IO Configuration using the Edit VISA Configuration dialogs, each device entry is recorded in the registry.
If visa32.dll is not in the system path or has had its name changed IO Libraries not set up correctly.
The most common reason for this error is that the IO libraries did not install visa32.dll into a directory in the system path.
Another common reason for this error is that the IO libraries are not installed with Agilent Visa as the primary Visa implementation.
System error recorded: The specified module could not be found. IO Libraries version: M.01.01.04, Installation directory: C:\Program Files\Agilent\IO Libraries Agilent Visa is primary: False This system needs to remove the IO Libraries and re-install with Agilent Visa as primary. Could not generate interface information.
The most common cause for this error is that the IO libraries Visa installation is incorrect.
Service Account Information
This section contains IO libraries installation path, version, and configured interfaces, as shown (important entries are highlighted):
Service account as configured in the registry: LocalSystem Running as Local System. This is a potential problem, as running as Local System on some systems causes instrument IO to fail Privileges... SeTcbPrivilege, Act as part of the operating system SeCreateTokenPrivilege, Create a token object SeTakeOwnershipPrivilege, Take ownership of files or other objects SeCreatePagefilePrivilege, Create a pagefile SeLockMemoryPrivilege, Lock pages in memory SeAssignPrimaryTokenPrivilege, Replace a process level token SeIncreaseQuotaPrivilege, Increase quotas SeIncreaseBasePriorityPrivilege, Increase scheduling priority SeCreatePermanentPrivilege, Create permanent shared objects SeDebugPrivilege, Debug programs SeAuditPrivilege, Generate security audits SeSecurityPrivilege, Manage auditing and security log SeSystemEnvironmentPrivilege, Modify firmware environment values SeChangeNotifyPrivilege, Bypass traverse checking SeBackupPrivilege, Back up files and directories SeRestorePrivilege, Restore files and directories SeShutdownPrivilege, Shut down the system SeLoadDriverPrivilege, Load and unload device drivers SeProfileSingleProcessPrivilege, Profile single process SeSystemtimePrivilege, Change the system time SeUndockPrivilege, Remove computer from docking station SeManageVolumePrivilege, Perform volume maintenance tasks SeImpersonatePrivilege, Impersonate a client after authentication SeCreateGlobalPrivilege, Create global objects
Running the server under the Local System account on certain systems prevents the system from loading visa32.dll. If the IO is not functioning and all the IO libraries information is correct, run the service under an account with Administrator privileges.
Drive Types
As a security precaution, runtime versions of .NET will not allow running networked applications from removable media. Attempting to run the CM server from a removable drive will fail and issue a security exception.
Enumerating drive types...
C: Drive type: Fixed
D: Drive type: CdRom -- the server will not work when installed on this type of drive
R: Drive type: Remote -- the server will not work when installed on this type of drive
S: Drive type: Remote -- the server will not work when installed on this type of drive
Processes
This section contains a list of running processes. Important entries are highlighted, as shown:
Snapshot of running processes...
MsmtSrvc, Process id: 1280
DiagnosticServi, Process id: 744
CMD, Process id: 2080
mstask, Process id: 956
CTFMON, Process id: 1704
iprocsvr, Process id: 2024
SMSS, Process id: 204
TASKMGR, Process id: 2128
ati2evxx, Process id: 628
adcist, Process id: 1696
IDA, Process id: 1588
MsmtSrvr, Process id: 2056
Directcd, Process id: 1692
winvnc, Process id: 1048
IDASched, Process id: 1740
iproc82357, Process id: 936
PageMill, Process id: 732
LSASS, Process id: 292
WinMgmt, Process id: 1040
svchost, Process id: 504
OSA, Process id: 1572
CreateCD50, Process id: 1676
mdm, Process id: 712
SERVICES, Process id: 280
nutsrv4, Process id: 916
explorer, Process id: 1448
WZQKPICK, Process id: 1768
VPTray, Process id: 1660
ltmoh, Process id: 1552
CMD, Process id: 1764
NMSSvc, Process id: 800
epsilon, Process id: 1292
SynTPEnh, Process id: 1332
realsched, Process id: 1652
CMServerDiagnos, Process id: 1972
SynTPLpr, Process id: 1436
regsvc, Process id: 352
DefWatch, Process id: 676
Eudora, Process id: 1744
SMTray, Process id: 1636
ltmsg, Process id: 1528
atiptaxx, Process id: 1420
svchost, Process id: 456
CSRSS, Process id: 232
WINLOGON, Process id: 228
CMD, Process id: 2160
Crypserv, Process id: 660
spoolsv, Process id: 552
Rtvscan, Process id: 872
iproc488, Process id: 2048
PROMon, Process id: 1512
EABSERVR, Process id: 1508
CMD, Process id: 116
System, Process id: 8
prpcui, Process id: 1612
bash, Process id: 752
Idle, Process id: 0
For the IO libraries to work, the processes named iprocsvr , iproc488 , and iproc82357 must be running. In 2003C, if these processes are not running, the CM server will start them. Prior to that, the processes started when somebody interactively logged into the server PC. If IO isn't working, one potential problem in 2003A is that no user is logged onto the server PC.
Directory Contents
This section contains a list of the server installation directory contents and revision information for each file. The measurement DLLs are in the ImportedAssemblies directory. The CM server revision for 2004A is 3.0.2004.1.
Directory contents...
C:\Program Files\Agilent\Connection Manager Server\Agilent.TMFramework.dll, Version: 1.0.4230.0
C:\Program Files\Agilent\Connection Manager
Server\Agilent.TMFramework.InstrumentDriverInterop.dll, Version: 1.0.4230.0
C:\Program Files\Agilent\Connection Manager
Server\Agilent.TMFramework.InstrumentIO.Configuration.dll, Version: 1.0.4230.0
C:\Program Files\Agilent\Connection Manager Server\Agilent.TMFramework.InstrumentIO.dll, Version:
1.0.4230.0
C:\Program Files\Agilent\Connection Manager
Server\Agilent.TMFramework.InstrumentIO.VisaInterop.dll, Version: 1.0.4230.0
C:\Program Files\Agilent\Connection Manager Server\Agilent.TMFramework.InternalUtils.dll, Version:
1.0.4230.0
C:\Program Files\Agilent\Connection Manager Server\CMDiagnostics.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\CMServerDiagnostics.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\HwCatalog.dll, Version: 0.0.0.0
C:\Program Files\Agilent\Connection Manager Server\IsAdmin.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\LibMgr.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\MsmtEvents.dll, Version: 0.1.0.0
C:\Program Files\Agilent\Connection Manager Server\PowerManagement.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\VisaIO.dll, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\vsassert.dll, Version: 7.0.9466.0
C:\Program Files\Agilent\Connection Manager Server\CMController.exe, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\MsmtSrvc.exe, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\MsmtSrvr.exe, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\VisaInstFinder.exe, Version: 3.0.2004.1
C:\Program Files\Agilent\Connection Manager
Server\ImportedAssemblies\AGE444XAVxipnpNETWrapper.dll, Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\Agilent8753.dll, Version:
0.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\ESGBServer.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\ESGCServer.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\HP856XEVxipnpNETWrapper.dll,
Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\HP859XEVxipnpNETWrapper.dll,
Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\HP871XVxipnpNETWrapper.dll,
Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\HPE4406VxipnpNETWrapper.dll,
Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\HPESGVxipnpNETWrapper.dll,
Version: 1.0.0.0
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\ScopeServer.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\SparmServer.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\SparmServerPNA.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\SpectrumServer.dll, Version:
3.0.2004.1
C:\Program Files\Agilent\Connection Manager Server\ImportedAssemblies\VSAServer.dll, Version:
3.0.2004.1
Plug and Play Driver Information
This section contains a list of the VISA Plug and Play drivers and revision information for each file. ADS measurements require the highlighted DLLs shown below.
Plug and Play driver installation directory: C:\Program Files\VISA\winnt.
C:\Program Files\VISA\winnt\bin\AG875XVxipnpNETWrapper.dll, Version: 1.0.0.0
C:\Program Files\VISA\winnt\bin\AGE444XAVxipnpNETWrapper.dll, Version: 1.0.0.0
C:\Program Files\VISA\winnt\bin\age444xa_32.dll, Version: 1.0.0.1
C:\Program Files\VISA\winnt\bin\hp548xx_32.dll
C:\Program Files\VISA\winnt\bin\hp856xe_32.dll, Version: 1.0.0.0
C:\Program Files\VISA\winnt\bin\hp859xe_32.dll, Version: 1.0.0.0
C:\Program Files\VISA\winnt\bin\hp871x_32.dll
C:\Program Files\VISA\winnt\bin\hpe4406_32.dll, Version: 1.0.0.1
C:\Program Files\VISA\winnt\bin\HPESGVxipnpNETWrapper.dll, Version: 1.0.0.0
C:\Program Files\VISA\winnt\bin\hpesg_32.dll, Version: 1.0.0.1
C:\Program Files\VISA\winnt\bin\hpgpvx32.dll, Version: 77.1.1.4
C:\Program Files\VISA\winnt\bin\ag875x_32.dll, Version: 1.0.0.1
Module Information
This section contains a list of the modules loaded into the MsmtSrvr.exe process. This information contains the versions of system and measurement libraries the server actually has loaded in memory.
Module information for MsmtSrvr... Module name: MsmtSrvr.exe File: C:\Program Files\Agilent\Connection Manager Server\MsmtSrvr.exe InternalName: MsmtSrvr.exe OriginalFilename: MsmtSrvr.exe FileVersion: 5.0.2006.1 FileDescription: Agilent Connection Manager Product: Agilent Connection Manager ProductVersion: 5.0.2006.1 Debug: False Patched: False PreRelease: False PrivateBuild: False SpecialBuild: False Language Language Neutral Module name: ntdll.dll File: C:\WINDOWS\system32\ntdll.dll InternalName: ntdll.dll OriginalFilename: ntdll.dll FileVersion: 5.1.2600.2180\(xpsp_sp2_rtm.040803-215\) FileDescription: NT Layer DLL Product: Microsoft� Windows� Operating System ProductVersion: 5.1.2600.2180 Debug: False Patched: False PreRelease: False PrivateBuild: False SpecialBuild: False Language English (United States)
System Information
This section contains a description of the server PC memory, operating system, and processor. Important entries are highlighted, as shown:
Memory information...
Total Physical Memory: 527941632
Free Physical Memory: 281899008
Total Page File: 1289859072
Free Page File: 1006911488
Total Virtual Memory: 2147352576
Free Virtual Memory: 1947172864
Operating system information...
Microsoft Windows XP
Uniprocessor Free
Service Pack 1
Processor information...
Registry key: 0
Registry name: Component Information, Registry value: System.Byte[ ]
Registry name: Identifier, Registry value: x86 Family 15 Model 2 Stepping 4
Registry name: Configuration Data, Registry value:
Registry name: ProcessorNameString, Registry value: Intel® Pentium® 4 Mobile CPU
1.70GHz
Registry name: VendorIdentifier, Registry value: GenuineIntel
Registry name: FeatureSet, Registry value: 12287
Registry name: ~MHz, Registry value: 1694
Registry name: Update Status, Registry value: 0
Registry name: Update Signature, Registry value: System.Byte[ ]
Registry name: Previous Update Signature, Registry value: System.Byte[ ]
New, higher-speed computers with fast HPIB interfaces can overload old, slower instruments. By recording the processor clock speed and the IO Libraries information above, EEsof support engineers can help diagnose these data overflow problems.
If the PC has more than one processor, there will be additional entries with headings like Registry key: 1 and so on.
Privacy
Statement 
|
Terms of Use |
Legal |
Contact Us |
© Agilent 2000-2008
