RTC stopped working, ArgumentOutOfRange

toLLto

Strange problem, one user cannot start the RTC, the error is:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: microsoft.dynamics.nav.client
Problem Signature 02: 6.0.0.0
Problem Signature 03: 4d030e65
Problem Signature 04: mscorlib
Problem Signature 05: 2.0.0.0
Problem Signature 06: 4e154c6c
Problem Signature 07: e2
Problem Signature 08: 16
Problem Signature 09: System.ArgumentOutOfRange
OS Version: 6.1.7600.2.0.0.16.7
Locale ID: 1031

Same error when user try to run a page in Classic client.

Other users can run RTC without errors.

I read this topic:
http://www.mibuso.com/forum/viewtopic.php?f=32&t=44066&p=247434

but didn't help me.

Troelsh

Sounds strange ... Have you checked that this particular client is not running with some special regional settings or has something special in clientusersettings.config ?

toLLto

Troelsh wrote:

Sounds strange ... Have you checked that this particular client is not running with some special regional settings or has something special in clientusersettings.config ?

nothing unusual, clientusersettings.config same as other users, no special regional settings....

I tried to make this user a member of the local Administrators group - same error.

Fuppe

I experience the same problem. Have anyone found a solution?

skulla

Did you try to change his profile ID as others whose RTC client is working ?

Fuppe

Yes, i have tried to change the profile ID to one that i working. I have also tried to delete all files in the user folder that has anything to do with NAV. If i delete the hole folder under documents and settings -> username NAV will use the TEMP userfolder and then it works.

manisharma31

Had you tried with other machine where RTC is working fine for that user.

Have there been any updates installed on the machine.

beran

Are you running the latest update? I have seen that being the solution.

Have you taken a look in the event viewer/log? It sometimes have an entry which shows the entire exception list with stacks for the crash.

Fuppe

The customer is running version 2009 R2, and to my knowledge there hasn't been any service packs for that version. I have looked in the eventviewer but there was nothing
there that gave me a hint to the error..

Troelsh

There has been several hotfixes for the R2 release - the latest build no is 6.0.33639 (kb 2734394)

Go to partnersource to grab that

lilkou

Hi , I have the same problem, for any time, before RTC started without problem.
Now stops with the same error:
Some users can still run RTC , the other ones - became the ERRROR. :-k



Beschreibung:
Stopped working

Problemsignatur:
Problemereignisname: CLR20r3
Problemsignatur 01: microsoft.dynamics.nav.client
Problemsignatur 02: 6.0.0.0
Problemsignatur 03: 4d030e65
Problemsignatur 04: mscorlib
Problemsignatur 05: 2.0.0.0
Problemsignatur 06: 5174ddfb
Problemsignatur 07: e2
Problemsignatur 08: 16
Problemsignatur 09: System.ArgumentOutOfRange
Betriebsystemversion: 6.1.7601.2.1.0.18.10
Gebietsschema-ID: 1031

Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt

mihail_kolev

One of the weirdest problems I've ever met. After a couple of ProcessMonitor sessions we saw something strange. At some point there are some calls to the registry:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices\{some printer name}

there was listed all of the installed printers and more. So, when a user run normaly the RTC these entries was looking good. But when the other user try to run it, there was a strange entry:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices\??????? ??? OneNote 2013

Actually when we opened the registry folder, the question marks was Cyrillic symbols - "Изпрати към OneNote 2013" (plain Bulgarian =P~ )

After deleting these entries, the user was able to run the RTC again. (YAY \:D/ )

But why these entries was there and why they are bad? Well, this is a terminal server machine with German regional settings. So, when somebody connect with Remote Desktop and share his/her printers, the terminal server register these printers for the current user. Obviously the RTC loads all printers on startup. As we know the RTC (R2) is not unicode, so it can't handle these characters. Once this is done, the user can't open the RTC until the bad entries are removed.

I hope this will help to some poor soul out there [-o<

afarr

Thanks Mihail. One of our clients had the same problem, and your solution worked for them too.