[Su...] Posted September 17, 2021 Share Posted September 17, 2021 Can someone explain what this means? Had a power failure and this warning pops up with no information visible. Click OK and it will close. Thank You! Link to comment Share on other sites More sharing options...
[No...] Posted September 20, 2021 Share Posted September 20, 2021 My bet is on some damaged (config?) file. Update: The string 'userDic' seems to appear only in 'inspection' and 'inspset' files, followed by protocol header variables. Very wild guess: If the warning pops up without any measurement plan opened, maybe Calypso goes through the last opened plans and tries to read that data section, failing at one damaged inspection/inspset file? I would try and check the last used measurement plans on the start page for integrity. Worth a try at least. Link to comment Share on other sites More sharing options...
[Br...] Posted September 20, 2021 Share Posted September 20, 2021 A new config would be the first thing to try. This message is nothing but an annoyance. If a new config doesnt do the trick, then i would suggest uninstall/reinstall Calypso and the service pack. Link to comment Share on other sites More sharing options...
[Su...] Posted September 22, 2021 Author Share Posted September 22, 2021 Thanks for the replies! After a few reboots and opening, running, saving the last program, the warning has not returned. Link to comment Share on other sites More sharing options...
[An...] Posted January 28 Share Posted January 28 englisch below Hallo zusammen, wir hatten heute die selbe Fehlermeldung "Problem at reading userDIc from file at:" Es hat sich herausgestellt, dass es an der Protokollkopfvariable lag, diese wurde zwar seit längerer Zeit nicht geändert, hier kam aber die Fehlermeldung "Sonderzeichen nicht erlaubt". Wir haben die Protokollkopfvariable neu hereingeladen und die Messprogramm überspeichert, der Fehler wurde somit behoben. -- Hello everyone, today we had the same error message “Problem at reading userDIc from file at:” It turned out that it was due to the log header variable, which had not been changed for a long time, but the error message “Special characters not allowed” was displayed. We reloaded the log header variable and saved the measurement program, which fixed the error. Link to comment Share on other sites More sharing options...
[Je...] Posted January 28 Share Posted January 28 Please sign in to view this quote. Isn't it nice when problems basically resolve themselves? Glad this was a fairly simple fix. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in