You’re offline. This is a read only version of the page.
Hi all,
Came across an issue with terminal services that might be worth noting for the future / be of interest to you.
Our client placed a support query saying that in the Sales Document Enquiry window, if they selected a SOP document and drilled back to it, it took about 5 minutes for the document to load. This only happened with certain documents, though, and there was no pattern in the documents that were slow to load.
After exhaustive investigation (pure trial and error stuff), I eventually noticed that the dex.ini file had a large number of unusual entries in it. These were something like 'spooler 0001 (plus various other texts, sometimes an IP address). I discovered through trial and error, that if I deleted these 'strange' lines from the dex.ini file that the performance issue was solved!...
It seems that each time a user logged into remote desktop and accessed Gp on the terminal server, the terminal services checked if any printers were installed locally on the users desktop...and added a line in the dex.ini file for any printers it found (???)...(any lines with an IP address quoted...the IP address was of a network printer)
I then found a techknowledge on a similar issue (lines being added to the dex.ini file)...but this was a known issue only if Named Printers had been enabled (which they hadn't been on our customers site).
At the moment, I log in to our customers site once per week and replace the dex.ini file with a back up (one without any of the strange entries)...This is just maintenance untill I can find a permanent solution. There are settings in TS that tell it to allow users print to a local printer. I have tested with this option set on and off, and it makes no difference.
Anyway, just thought I'd share this with you all. If you get unusual (unusual in that it only happened with some documents)...performance issues in enquiry windows and you use TS, its worth eviewing the dex.ini file. I'm intrigued by the fact that it only happens on some SOP documents..(same documents every time)...I working on a theory that it has something to do with whether or not the SOP document was ever printed...This is the only possible link between these documents I can think of...and also since it is printer related...maybe clutching at straws with that theory!!
Has anyone come across this before? Did you find a permanent solution?
Best regards, Ian.
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
1