*This post is locked for comments
*This post is locked for comments
You might find the following KB article helpful:
support.microsoft.com/.../2027739
In it, it discusses creating a batch file to delay the opening of Microsoft Dynamics SL. This gives an opportunity for the processes to complete. The article specifically references issues with printers loading, but I think it could apply to other situations as well.
Thanks Rachel. Yes I believe we are using it as a RemoteApp. Anything I can do to prevent this problem from recurring? (It hasn't happened again since last week but just in case.)
Hi Chipdex,
Do you have SL published as a RemoteApp? It sounds like some function is getting delayed and causing problems in calling other functions that rely on it. I ask because when using RemoteApp, some start-up procedures are not performed.
I had someone get this same exact error today. We are using Windows 7 64-bit linked clones in a Vmware View 5.0 environment. After logging off and back on SL loaded properly. Any thoughts?
Hello RedStorm,
I was not able to find any reports of that error message. Could I get a little more information from you regarding the error?
- What is the OS of the Terminal Server?
- Is the TS a virtual machine? If yes, is it VMWare, Hyper-V, etc.?
- Is SL set up as a Published App?
- Does this happen for all user or do only a certain few see this message?
- It sounds like it does not happen every time, but randomly. Could you confirm this?
I'm not sure what would be causing this issue. It's possible that the client installation got corrupted somehow. I'm not entirely sure. You may try uninstalling and reinstalling only the client piece on the TS. Please be sure that you are logged in as a local administrator and that UAC is turned off when performing the SL installation.