| Author | Message |
|---|---|
|
boiner_george |
Message 45832 — Posted: 7 Apr 2013, 16:45:20 UTC Receiving run time error after increasing disk space for this hard disk eating hog … added another 2gig. After doing this, apparently, it is the only change I’ve made to BOINC stuff in the last couple of weeks … or for that matter to my machine … other then loading the latest version of Java … I get the following. forrtl: sever (19) invalid reference to variable in NAMELIST C:ProgramDataBOINCprojectsclimateprediction.nethadcm3n_zg88_1920 ….climate.cpdc line 528, position 8. …. stack trace terminate abnormally. Anybody out there got a clue? Running Pentium i7-2600K CPU 3.5GHz, with 16 gig RAM, NVIDIA 690 video card, Windows 7 64 bit Operating System … tons of hard disk ID: 45832 · |
|
|
Message 45834 — Posted: 7 Apr 2013, 18:58:40 UTC I had a potload of them yesterday, on different machines. Each one threw six Fortran error popups, then crashed. No pattern was noticed in the Task names but, given that it was consistent across seven Intel quads from Q6600 to i5 3550, with OSs from XP_x64 to W7_x64, I chock it up to a problem with a large chunk of the few thousand Tasks released recently. All failed to start. Work units for those with a «history» showed the same problem. CPDN’s Data file «growth» comes from the inability of CPDN to clean-up after itself after abnormal endings. Frustrating, isn’t it? (I’ve been remiss in cleaning-up after failures for a long time and have Data files ranging up to a ridiculous 16Meg…) Edit: The link in my footer no longer works: It hasn’t been updated because I have hope (probably vain) that our original board will be resurrected. «We have met the enemy and he is us.» — Pogo ID: 45834 · |
|
Arn |
Message 45836 — Posted: 7 Apr 2013, 20:43:54 UTC I’ve been receiving the Intel Visual Fortran run-time error continuously for the second day now, but the error reads somewhat differently: forrtl: severe (19): invalid reference to variable in NAMELIST input, unit 5, file Image PC Routine Line Source I have ended work for Climate Prediction until I am assured no damage will result from this error. I googled this and the very first stated ‘severe’ must be corrected. Any knowledgeable assistance will be appreciated. Thanks. tcpk22 ID: 45836 · |
|
Lockleys |
Message 45837 — Posted: 7 Apr 2013, 21:13:06 UTC I have just experienced a similar message set to Arn for task hadcm3n_3l4z_1980_40_008349369_2 . I have aborted it. ID: 45837 · |
|
Les Bayliss |
Message 45838 — Posted: 7 Apr 2013, 21:27:57 UTC Arn All «severe» means is that the error will most likely be fatal TO THE COMPUTER PROGRAM THAT HAS HAD THIS. i.e. the climate model. ID: 45838 · |
|
Les Bayliss |
Message 45839 — Posted: 7 Apr 2013, 21:30:11 UTC I’ve had a PM about this error, as well as those reported here, so I’ll let the project people know. ID: 45839 · |
|
Ironworker16 |
Message 45840 — Posted: 7 Apr 2013, 23:02:43 UTC — in response to Message 45832. I have the same error here also. I�m Including the Error text & stderr.txt from one work unit. I’m going to suspend the project unit until there is a resolution. ————————— Image PC Routine Line Source ————————— stderr.txt — Notepad 04:25:22 (76312): No heartbeat from core client for 30 sec — exiting Running core i7-920 CPU , with 12 gig RAM, Radeon HD 7970 video card, Windows 8 64 bit Operating System … tons of hard disk ID: 45840 · |
|
|
Message 45841 — Posted: 8 Apr 2013, 1:15:55 UTC Thanks to everyone for your reports. The reason the errors say Visual Fortran is that this is the language the climate models are written in. Here is a list of Fortran Run-Time error codes with very brief descriptions of their meanings. I had downloaded three new models yesterday, Sunday, but they hadn’t begun to run. So I suspended some models already running to make the new ones start. Here’s what happened: Within seconds of starting each of the three models threw a Visual Fortran Runtime error just like the ones members have already quoted. Two models starting in 1980 said the error was in line 529 in position 0, whereas the model starting in 1920 said line 528 in position 8. I left the models running and opened Windows Event Viewer to see whether the three runtime errors were recorded there. I could find no trace of these errors either by name or by timestamp. They appeared to have had no effect on the running of the computer. I then looked at the Fortran error page again and noticed that ‘with severe, program execution stops (unless a recovery method is specified)’. My models still seemed to be running in the sense that they were still clocking up time. I opened the graphics window for each of them to see how they were advancing and found that all three were stopped at timestep No 1 and showed completely blue globes. Blue is the default colour and means that computation never started. I checked in Windows Task Manager Performance tab to see whether these models were using CPU time (and energy/electricity) and found that they were idle ie costing no energy. As these models are not advancing I’m going to abort them and get new ones. But if the new ones belong to the same batch they will probably throw the same error. Visual Fortran Runtime errors have never in the past done any harm to our computers. As Les has said, this error is restricted to the model in question. It looks scary because of the cross in the red circle but is harmless to everything except the models. Look at the graphics to see whether they’re really processing and if they’re not, please abort them.
Cpdn news ID: 45841 · |
|
Les Bayliss |
Message 45842 — Posted: 8 Apr 2013, 16:15:13 UTC OK, the problem has been traced to an incorrect line, (1 of hundreds), in one of the many files that go to make up data sets to start these models. Thank goodness people buy cars assembled, and don’t get dozens of boxes of various shapes and sizes with parts that they then have to assemble themselves. With the instructions, no doubt, in the language of origin of the parts makers. ID: 45842 · |
|
zombie67 [MM] |
Message 45845 — Posted: 8 Apr 2013, 22:48:37 UTC I received several of these too. Will the bad tasks be aborted server-side? Reno, NV ID: 45845 · |
|
Les Bayliss |
Message 45846 — Posted: 9 Apr 2013, 0:05:50 UTC — in response to Message 45845. Bad tasks on Macs and Linux should self abort very quickly. ID: 45846 · |
|
|
Message 45847 — Posted: 9 Apr 2013, 0:10:08 UTC Hi Zombie To my knowledge, tasks already sent to computers won’t be aborted from the server. This was done once before but the killer message was sent from the server to the computer when the model’s next trickle was uploaded. But AFAIK this can’t be done with the current models because although they’re accumulating runtime they are making no progress and will never reach the end of their first year which is when they would normally trickle up and make contact with the server. I get the impression from looking at a lot of these models’ task and WU web pages that on Darwin and Linux many of the models crash of their own accord. They don’t all crash on Windows. On my own Windows machine three of these models accumulated runtime for well over an hour without making progress, using CPU time or crashing. Other longer periods have been reported in this thread. I think a lot of these models are still stuck on computers. Not using electricity but hogging CPU cores that could be crunching usefully. Please abort them. I know this is tedious for members who have a lot of computers. I see Les got there first but I’ll leave my comments anyway Cpdn news ID: 45847 · |
|
zombie67 [MM] |
Message 45848 — Posted: 9 Apr 2013, 2:40:03 UTC Yes, I am talking about windows machines here. But the bad tasks should be aborted from the server-side, all the same. The machine will likely contact the server to fill a different thread slot, and would then learn to kill the task. There is no reason to *not* kill those bad tasks from the server side: If *nix: They die anyway Reno, NV ID: 45848 · |
|
Les Bayliss |
Message 45849 — Posted: 9 Apr 2013, 3:07:19 UTC — in response to Message 45848. For the «killer trickle» to be sent to the correct target, that target, i.e. climate model, needs to return a trickle_up file for the server to find it. ID: 45849 · |
|
|
Message 45850 — Posted: 9 Apr 2013, 7:12:47 UTC — in response to Message 45842. Thank goodness people buy cars assembled, and don’t get dozens of boxes of various shapes and sizes with parts that they then have to assemble themselves. With the instructions, no doubt, in the language of origin of the parts makers. Thank goodness people buy cars assembled, and don’t get dozens of boxes of various shapes and sizes with parts that they then have to assemble themselves. With the instructions, no doubt, in the language of origin of the parts makers. Strangely, while you don�t buy cars that way you can buy airplanes. People buy disassembled kits that they have to put together themselves. Then they get in and fly them. Frightening isn�t it. ID: 45850 · |
|
|
Message 45851 — Posted: 9 Apr 2013, 7:31:09 UTC — in response to Message 45850. Wouldn’t know about the instructions bit — I only rtfm when something doesn’t work. ID: 45851 · |
|
Ingleside |
Message 45916 — Posted: 13 Apr 2013, 1:07:15 UTC — in response to Message 45849.
Aborting tasks without relying on trickle-messages has been part of BOINC since around BOINC-Client v5.10.x. ID: 45916 · |
|
MichaelO |
Message 45949 — Posted: 16 Apr 2013, 20:22:35 UTC Great discussion…I was concerned I was doing something wrong. However, after aborting tasks behaving like those described, one machine I have has not received any further tasks. Is this likely an unrelated issue? I.e., could aborting the tasks with errors ‘flag’ my machine so the server now ignores it? ID: 45949 · |
|
Les Bayliss |
Message 45950 — Posted: 16 Apr 2013, 20:49:46 UTC — in response to Message 45949. This project often has long periods of no work. This is one of them. See the Server Status page for what’s available. Blue menu to the left, 5 from the bottom. ID: 45950 · |
|
Pete(r) van der Spoel |
Message 45979 — Posted: 19 Apr 2013, 14:09:16 UTC — in response to Message 45842.
Does this happen automatically or do I need to abort the tasks? I’ve been getting these errors since yesterday but the progress % keeps creeping up and the graphics confirm that the tasks still seem to be progressing (colour pattern changes). ID: 45979 · |
Reply Quote
astroWX
When there is a run time error while I am debugging my application via Visual Studio 2013, I expect that the debugger should stop on the line that is causing the problem. However, the debugger unexpectedly stops on a C++ code line in another part of our application.
The details of what is occuring:
1. a traceback dialog box titled «Intel(r) Visual Fortran run-time error» appears. It has correct traceback source code and line information about where the error happens in the Fortran code. The dialog has a single «OK» button.
2. I click «OK»
3. Visual Studio produces a dialog box indicating that my application has triggered a breakpoint. It has two buttons, «Break» and «Continue»
4. I click «Break»
5. The debugger breaks in our C++ code in another thread.
6. I navigate the through all of the threads in the thread window and observe the call stack window for each thread to try and locate the Fortran thread, but it is already terminated
What should should I do to signal the debugger to stop on the Fortran source code line instead of producing the run-time error dialog box with the traceback information?
In VS2005 the behavior was for the debugger to stop in the Fortran source code and then when trying to continue the traceback information dialog box would be produced.
Our application is a C++ executable that calls Fortran dlls.
The Fortran compiler switches are as follows:
/nologo /debug:full /MP /Od /free /warn:interfaces /iface:cvf /module:»Debug» /object:»Debug» /Fd»Debugvc120.pdb» /traceback /check:all /libs:dll /threads /dbglibs /c
The linker switches are as follows:
/OUT:»Debugacerate.dll» /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:»acerate.dll.intermediate.manifest» /MANIFESTUAC:»level=’asInvoker’ uiAccess=’false’» /DEBUG /PDB:»acerate.pdb» /SUBSYSTEM:WINDOWS /IMPLIB:»acerate.lib» /DLL HTRILogging.lib
My system info:
Microsoft Visual Studio Premium 2013
Version 12.0.30110.00 Update 1
Microsoft .NET Framework
Version 4.5.50938
Installed Version: Premium
Intel(R) Visual Fortran Composer XE 2013 SP1 Update 2 Integration for Microsoft Visual Studio* 2013, 14.0.0086.12
| Author | Message |
|---|---|
|
boiner_george |
Message 45832 — Posted: 7 Apr 2013, 16:45:20 UTC Receiving run time error after increasing disk space for this hard disk eating hog … added another 2gig. After doing this, apparently, it is the only change I’ve made to BOINC stuff in the last couple of weeks … or for that matter to my machine … other then loading the latest version of Java … I get the following. forrtl: sever (19) invalid reference to variable in NAMELIST C:ProgramDataBOINCprojectsclimateprediction.nethadcm3n_zg88_1920 ….climate.cpdc line 528, position 8. …. stack trace terminate abnormally. Anybody out there got a clue? Running Pentium i7-2600K CPU 3.5GHz, with 16 gig RAM, NVIDIA 690 video card, Windows 7 64 bit Operating System … tons of hard disk ID: 45832 · |
|
|
Message 45834 — Posted: 7 Apr 2013, 18:58:40 UTC I had a potload of them yesterday, on different machines. Each one threw six Fortran error popups, then crashed. No pattern was noticed in the Task names but, given that it was consistent across seven Intel quads from Q6600 to i5 3550, with OSs from XP_x64 to W7_x64, I chock it up to a problem with a large chunk of the few thousand Tasks released recently. All failed to start. Work units for those with a «history» showed the same problem. CPDN’s Data file «growth» comes from the inability of CPDN to clean-up after itself after abnormal endings. Frustrating, isn’t it? (I’ve been remiss in cleaning-up after failures for a long time and have Data files ranging up to a ridiculous 16Meg…) Edit: The link in my footer no longer works: It hasn’t been updated because I have hope (probably vain) that our original board will be resurrected. «We have met the enemy and he is us.» — Pogo ID: 45834 · |
|
Arn |
Message 45836 — Posted: 7 Apr 2013, 20:43:54 UTC I’ve been receiving the Intel Visual Fortran run-time error continuously for the second day now, but the error reads somewhat differently: forrtl: severe (19): invalid reference to variable in NAMELIST input, unit 5, file Image PC Routine Line Source I have ended work for Climate Prediction until I am assured no damage will result from this error. I googled this and the very first stated ‘severe’ must be corrected. Any knowledgeable assistance will be appreciated. Thanks. tcpk22 ID: 45836 · |
|
Lockleys |
Message 45837 — Posted: 7 Apr 2013, 21:13:06 UTC I have just experienced a similar message set to Arn for task hadcm3n_3l4z_1980_40_008349369_2 . I have aborted it. ID: 45837 · |
|
Les Bayliss |
Message 45838 — Posted: 7 Apr 2013, 21:27:57 UTC Arn All «severe» means is that the error will most likely be fatal TO THE COMPUTER PROGRAM THAT HAS HAD THIS. i.e. the climate model. ID: 45838 · |
|
Les Bayliss |
Message 45839 — Posted: 7 Apr 2013, 21:30:11 UTC I’ve had a PM about this error, as well as those reported here, so I’ll let the project people know. ID: 45839 · |
|
Ironworker16 |
Message 45840 — Posted: 7 Apr 2013, 23:02:43 UTC — in response to Message 45832. ID: 45840 · |
|
|
Message 45841 — Posted: 8 Apr 2013, 1:15:55 UTC Thanks to everyone for your reports. The reason the errors say Visual Fortran is that this is the language the climate models are written in. Here is a list of Fortran Run-Time error codes with very brief descriptions of their meanings. I had downloaded three new models yesterday, Sunday, but they hadn’t begun to run. So I suspended some models already running to make the new ones start. Here’s what happened: Within seconds of starting each of the three models threw a Visual Fortran Runtime error just like the ones members have already quoted. Two models starting in 1980 said the error was in line 529 in position 0, whereas the model starting in 1920 said line 528 in position 8. I left the models running and opened Windows Event Viewer to see whether the three runtime errors were recorded there. I could find no trace of these errors either by name or by timestamp. They appeared to have had no effect on the running of the computer. I then looked at the Fortran error page again and noticed that ‘with severe, program execution stops (unless a recovery method is specified)’. My models still seemed to be running in the sense that they were still clocking up time. I opened the graphics window for each of them to see how they were advancing and found that all three were stopped at timestep No 1 and showed completely blue globes. Blue is the default colour and means that computation never started. I checked in Windows Task Manager Performance tab to see whether these models were using CPU time (and energy/electricity) and found that they were idle ie costing no energy. As these models are not advancing I’m going to abort them and get new ones. But if the new ones belong to the same batch they will probably throw the same error. Visual Fortran Runtime errors have never in the past done any harm to our computers. As Les has said, this error is restricted to the model in question. It looks scary because of the cross in the red circle but is harmless to everything except the models. Look at the graphics to see whether they’re really processing and if they’re not, please abort them.
Cpdn news ID: 45841 · |
|
Les Bayliss |
Message 45842 — Posted: 8 Apr 2013, 16:15:13 UTC OK, the problem has been traced to an incorrect line, (1 of hundreds), in one of the many files that go to make up data sets to start these models. Thank goodness people buy cars assembled, and don’t get dozens of boxes of various shapes and sizes with parts that they then have to assemble themselves. With the instructions, no doubt, in the language of origin of the parts makers. ID: 45842 · |
|
zombie67 [MM] |
Message 45845 — Posted: 8 Apr 2013, 22:48:37 UTC I received several of these too. Will the bad tasks be aborted server-side? Reno, NV ID: 45845 · |
|
Les Bayliss |
Message 45846 — Posted: 9 Apr 2013, 0:05:50 UTC — in response to Message 45845. Bad tasks on Macs and Linux should self abort very quickly. ID: 45846 · |
|
|
Message 45847 — Posted: 9 Apr 2013, 0:10:08 UTC Hi Zombie To my knowledge, tasks already sent to computers won’t be aborted from the server. This was done once before but the killer message was sent from the server to the computer when the model’s next trickle was uploaded. But AFAIK this can’t be done with the current models because although they’re accumulating runtime they are making no progress and will never reach the end of their first year which is when they would normally trickle up and make contact with the server. I get the impression from looking at a lot of these models’ task and WU web pages that on Darwin and Linux many of the models crash of their own accord. They don’t all crash on Windows. On my own Windows machine three of these models accumulated runtime for well over an hour without making progress, using CPU time or crashing. Other longer periods have been reported in this thread. I think a lot of these models are still stuck on computers. Not using electricity but hogging CPU cores that could be crunching usefully. Please abort them. I know this is tedious for members who have a lot of computers. I see Les got there first but I’ll leave my comments anyway Cpdn news ID: 45847 · |
|
zombie67 [MM] |
Message 45848 — Posted: 9 Apr 2013, 2:40:03 UTC Yes, I am talking about windows machines here. But the bad tasks should be aborted from the server-side, all the same. The machine will likely contact the server to fill a different thread slot, and would then learn to kill the task. There is no reason to *not* kill those bad tasks from the server side: If *nix: They die anyway Reno, NV ID: 45848 · |
|
Les Bayliss |
Message 45849 — Posted: 9 Apr 2013, 3:07:19 UTC — in response to Message 45848. For the «killer trickle» to be sent to the correct target, that target, i.e. climate model, needs to return a trickle_up file for the server to find it. ID: 45849 · |
|
|
Message 45850 — Posted: 9 Apr 2013, 7:12:47 UTC — in response to Message 45842. ID: 45850 · |
|
|
Message 45851 — Posted: 9 Apr 2013, 7:31:09 UTC — in response to Message 45850. Wouldn’t know about the instructions bit — I only rtfm when something doesn’t work. ID: 45851 · |
|
Ingleside |
Message 45916 — Posted: 13 Apr 2013, 1:07:15 UTC — in response to Message 45849.
Aborting tasks without relying on trickle-messages has been part of BOINC since around BOINC-Client v5.10.x. ID: 45916 · |
|
MichaelO |
Message 45949 — Posted: 16 Apr 2013, 20:22:35 UTC Great discussion…I was concerned I was doing something wrong. However, after aborting tasks behaving like those described, one machine I have has not received any further tasks. Is this likely an unrelated issue? I.e., could aborting the tasks with errors ‘flag’ my machine so the server now ignores it? ID: 45949 · |
|
Les Bayliss |
Message 45950 — Posted: 16 Apr 2013, 20:49:46 UTC — in response to Message 45949. This project often has long periods of no work. This is one of them. See the Server Status page for what’s available. Blue menu to the left, 5 from the bottom. ID: 45950 · |
|
Pete(r) van der Spoel |
Message 45979 — Posted: 19 Apr 2013, 14:09:16 UTC — in response to Message 45842.
Does this happen automatically or do I need to abort the tasks? I’ve been getting these errors since yesterday but the progress % keeps creeping up and the graphics confirm that the tasks still seem to be progressing (colour pattern changes). ID: 45979 · |
Reply Quote
Error Message
Attempting to start or use any of the ArcGIS Desktop products returns a Visual Fortran Run-Time error.
Cause
This error may occur when the system locale and the user locale in the Regional Options are not set correctly. ArcGIS loads the appropriate code page files, which are used internally by ArcGIS to support various languages and character sets, to perform language-related operations using both the system locale and the user locale settings.
Solution or Workaround
In order for ArcGIS to run properly under a selected language environment, the same language setting must be selected for the system default locale and the user locale. This procedure must be completed from the administrator account.
<a href=’http://support.esri.com/en/knowledgebase/techarticles/detail/27176′ target=’_blank’>How To: Configure Windows to run ArcGIS in a selected language environment</a>
Related Information
- Microsoft Global Development and Computing Portal
Last Published: 5/5/2016
Article ID: 000005098
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS
Contact US
Thanks. We have received your request and will respond promptly.
Log In
Come Join Us!
Are you an
Engineering professional?
Join Eng-Tips Forums!
- Talk With Other Members
- Be Notified Of Responses
To Your Posts - Keyword Search
- One-Click Access To Your
Favorite Forums - Automated Signatures
On Your Posts - Best Of All, It’s Free!
*Eng-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.
Posting Guidelines
Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Students Click Here
visual fortran runtime errorvisual fortran runtime error(OP) 28 May 10 11:04 hey, visual fortran runtime error forrtl: severe (38): error during write, unit 70, does anybody knows this problem? thanks so far Wolfgang Red Flag SubmittedThank you for helping keep Eng-Tips Forums free from inappropriate posts. |
Resources
Learn methods and guidelines for using stereolithography (SLA) 3D printed molds in the injection molding process to lower costs and lead time. Discover how this hybrid manufacturing process enables on-demand mold fabrication to quickly produce small batches of thermoplastic parts. Download Now
Examine how the principles of DfAM upend many of the long-standing rules around manufacturability — allowing engineers and designers to place a part’s function at the center of their design considerations. Download Now
Metal 3D printing has rapidly emerged as a key technology in modern design and manufacturing, so it’s critical educational institutions include it in their curricula to avoid leaving students at a disadvantage as they enter the workforce. Download Now
This ebook covers tips for creating and managing workflows, security best practices and protection of intellectual property, Cloud vs. on-premise software solutions, CAD file management, compliance, and more. Download Now |
Join Eng-Tips® Today!
Join your peers on the Internet’s largest technical engineering professional community.
It’s easy to join and it’s free.
Here’s Why Members Love Eng-Tips Forums:
Talk To Other Members- Notification Of Responses To Questions
- Favorite Forums One Click Access
- Keyword Search Of All Posts, And More…
Talk To Other MembersRegister now while it’s still free!
Already a member? Close this window and log in.
Join Us Close
You get the updates by logging in to the Intel Registration Center. If you have not registered your serial number, do it here first. Once registered, you will receive a notice of all updates.
Your DLL project links to the Debug Multithreaded DLL libraries, which is the default on a debug configuration, but your C++ project has overridden that option and specifies the non-debug Multithreaded DLL libraries, resulting in the linker warning. It does not affect the run-time error.
Did you know that you can have both projects in the same solution, and have the DLL project a «dependent» of the executable? This will link in the DLL export library automatically.
I’m running some simulations in Matlab (solving an inverse problem) on a remote computer running on windows 7 and I’m using a loop in which I call for Ansys Mechanical to do some calculation before using the results.
It was running fine but after several iterations (87) I received an error coming from Ansys Mechanical See the error
Closing this window close Ansys Mechanical and after reopening it, I have the following Ansys Mechanical APDL Launcher Error: «Cannot create required ‘//mypath/../AppData/Ansys/v150/launcher/profiles.lock’ file. Therefore, cannot write to profile information during this launcher session» By clicking on OK on other window open saying «The launcher menu option ‘Write Laucnher Log File’ is selected. However, because you currently only have read access to the launcher profile, you will also not be permitted to write to the launcher log file during this launcher session».
After that, I can sometimes restart my simulation after a while (which will stop after a certain number of iterations) but if I want to start it again just after having seen the error, I get the Fortran error during the first iteration.
I don’t know much about Fortran and I haven’t seen any similar post. Have any of you already had this issue ?
Thanks for the help,
Nathan
Error Message
Attempting to start or use any of the ArcGIS Desktop products returns a Visual Fortran Run-Time error.
Cause
This error may occur when the system locale and the user locale in the Regional Options are not set correctly. ArcGIS loads the appropriate code page files, which are used internally by ArcGIS to support various languages and character sets, to perform language-related operations using both the system locale and the user locale settings.
Solution or Workaround
In order for ArcGIS to run properly under a selected language environment, the same language setting must be selected for the system default locale and the user locale. This procedure must be completed from the administrator account.
<a href=’http://support.esri.com/en/knowledgebase/techarticles/detail/27176′ target=’_blank’>How To: Configure Windows to run ArcGIS in a selected language environment</a>