You’re offline. This is a read only version of the page.
330
This occurred on SP3 and still occurs after upgrading to SP4. It does not happen on the application server, only on the terminal servers. We have already run SQL traces and we do not see an issue there. It does not happen to everyone, only some users. The users are already in the SL ADMINISTRATORS group. We have deleted and recreated profiles.
Version=1
EventType=CLR20r3
EventTime=129810577276581542
ReportType=2
Consent=1
UploadTime=129810577297641272
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=4011000.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=7.0.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=4dbfc08c
Sig[3].Name=Problem Signature 04
Sig[3].Value=Solomon.Kernel
Sig[4].Name=Problem Signature 05
Sig[4].Value=7.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=4903e6a9
Sig[6].Name=Problem Signature 07
Sig[6].Value=1b7
Sig[7].Name=Problem Signature 08
Sig[7].Value=0
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.Exception
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6002.2.2.0.16.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Dynamics\SL\Applications\OM\4011000.EXE
UI[3]=OM - Shippers has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=OM - Shippers
AppPath=C:\Program Files\Microsoft Dynamics\SL\Applications\OM\4011000.exe
ReportDescription=Stopped working
*This post is locked for comments
I have the same question (0)
Hi Philippe,
I understand you opened a case on this issue. Executing grant exec on GETAUTHENTICATIONTYPE to [Public] didn't resolve the issue. But in your case it was due to the solomon.ini file in the roaming profiles didn't have a Userid.
Share
Report
All responses (
Answers (
