Spirent TestCenter: Facing issue while saving the config file on the mapped drive
I have customer getting the below error while saving the config file on the particular mapped drive.(H:). As per received details. He has upgraded the chassis to 4.40 and seeing this issue. Please also find the below snapshot for the reference. “5/2/2014 07:07:56 .3 Error Other FileSaveCommand:” Whereas they are able to save the config file in the another mapped drive(O:) and locally. Below are the drive details. Customer is able to save another files on the mapped drive(H:) from other applications except Spirent TestCenter GUI. H:\ = \\KSTLMFPS01\ O:\ = \\KAAPAHDIP01N1\corpeng Has anyone met such issue before? Any suggestions are appreciated! ![![alt text][1]][1] Regards, Sandip Patil [1]: /storage/temp/4157-testsaveerror.jpg
Try removing the Spirent Communication folder in the local dir: Document settings - user - local - apppdata - spirent communication. Also, If they are on remote desktop, close the remote desktop and reconnect.
Hi Larry, I tried removing the Spirent Communication folder in the local Dir: Document settings - user - local - apppdata - spirent communication but still customer is facing the same issue. As per issue description, customer can save the file on different mapped drive (O:\ = \KAAPAHDIP01N1\corpeng) but not on the H:\ = \KSTLMFPS01\ Customer is complaning that, it was working fine before upgradation. Could you please suggest. Regards, Sandip Patil
This may not be the same situation as your customer but I have seen this when remote desktop to another PC while using the TestCenter GUI on that remote desktop. For some reason, although the remote desktop sees the mapped drive, the applications on that PC could not write to it. I had to log off the remote desktop PC and reconnect. Something to try if using remote desktop.,This may not be the same situation as your customer but I have seen this when remote desktop to another PC while using the TestCenter GUI on that remote desktop. For some reason, although the remote desktop sees the mapped drive, the applications on that PC could not write to it. I had to log off the remote desktop PC and reconnect.
15 People are following this question.
