Simple DataSocket example hangs the DataSocket server

[Sverre]

Hi,

 

I am having problems with the Simple DataSocket example. As soon as I try to connect to the DataSocket server on the local machine using dstp the server crashes. The error signature is:

AppName: cwdss.exe          AppVer: 4.2.3.1                 ModName: mfc42.dll

ModVer: 6.2.4131.0            Offset: 0001bc9b

By restarting the server I am sometimes able to connect but most of the time this only results in a repeated crash. Furthermore when I try to close either the reader or the writer after such a crash I get the error message “the RPC-server is not available”. The only way to close the program is to use the task manager. I am using Measurement Studio 7.1 and Visual Studio 2003 version 7.1.3088 and I have successfully used DataSocket to communicate with an OPC server on the local machine. I would appreciate any suggestions on how to solve the problems since I would like use dstp in my own applications.

Adam

[bilalD]

Hello

Looks like the datasocket component might have somehow ended up in a bad state. Try going to C:\Program Files\National Instruments\DataSocket, deleting cwdss.exe, and repairing Measurement Studio. That would force the installer to update the datasocket server components.

I hope this helps

[Sverre]

Thanks for the reply! I have done as you suggested but unfortunately this did not solve the problem. Have you got any other suggestions?

Adam

[bilalD]

Are you able to run any of the simple datasocket reader/writer examples. Try the simple datasocket reader and writer examples and see if you can get them to talk with each other. Did the datasocket files get replaced correctly after running the repair? What are the versions of the files? Also, what is the version of the nids.dll in the windows system32 folder?

[Sverre]

As I wrote in the original post, it is the simple datasocket example that I am having trouble with. I have managed to get the reader and writer to talk to each other by restarting the datasocket server repeatedly, but since the datasocket server crashes most of the times when I try to connect to it (i.e. I press either manual or auto update connect) this is rather tedious work. I think that the files were replaced correctly; at least the file cwdss.exe reappeared. The version of cwdss.exe is 4.2.3.1. Which other files should I check? The version of nids.dll is the same, i.e. 4.2.3.1.

Adam

[bilalD]

My bad, I thought you have modified the sample simple datasocket example. Your file versions look correct. I'm not sure why this might be happening. The only other thing I can think of right now is to re-install Measurement Studio and perhaps any other NI software that installs datasocket to fix any dependency issues that might be causing this.

Remove Measurement Studio via add/remove programs. Check to see once its uninstalled that the datasocket files mentioned previously were removed. If not, you can unregister the nids.dll from the system32 folder and delete it. Make sure to unregister the nids.dll before deleting it using regsvr32. You can delete the contents in the datasocket folder. Reboot and install Measurement Studio.

Make sure you have admin rights on the machine.

I hope this helps.

[Sverre]

I have now reinstalled every component of measurement studio and before doing so I made sure that every file had been deleted. This did not help. However, I tried installing measurement studio on another machine and on this everything seems to work fine. The machine it works on runs win2k while I’m running win xp pro. I suppose that this shouldn’t make a difference, or? I would very much like to get measurement studio to run on my own machine. What else could I try?

Adam

[bilalD]

Do you have another XP machine you could try this out on?

I have installed this fine on several XP Pro machines. I'm a little clueless now as to why this might be happening. Are you installing the software as an administrator? I'm not sure why your ds server would fail like this. It seems to crash at mfc42.dll, which is a windows system dll. So I don't know if there is something special about your system that is causing this. I have not seen anything like this before.

Ok, one more thing you could try is to use msiblast to make sure we remove everything. So first un-install using add/remove. Then run msiblast and see if there were any NI installer parts left over. Remove those, reboot and reinstall as admin.

I hope this helps.

[Sverre]

I finally found the solution to my problem by uninstalling various software on my PC. It seems like there is a conflict between Panda Platinum Antivirus and Datasocket. By uninstalling this program I managed to get Datasocket to work properly. I would like to point out that disabling Panda Antivirus entirely was not sufficient. I had to uninstall the program. Perhaps this is something you would like to look into.

Thanks for your efforts!

Adam