UHF - Header

Skip to main content
Dynamics 365 Community

SBX - Search With Button

SBX - Forum Post Title

Server failure 139

Microsoft Dynamics RMS Forum

Cerex asked a question on 13 Dec 2009 9:46 AM

Server failure 139

Suggested Answer
I recently moved a cash register to another location. I did not actually change anything, the hardware, software, or the IP settings. But ever since I moved it, I'm greeted with this error when attempting to start the POS software (not the admin or manager, however). Server Failure 139: Error occurred while attempting to read the register Since I received the error, I reinstalled the software, upgraded to SP2, and reinstalled drivers for all of the hardware. I still receive the same error. This problem has me stumped, has anybody else seen this problem before? Thanks in advance.
Reply
wescb responded on 18 Dec 2009 7:41 PM

Server failure 139

Unanswered
Does anyone know how to resolve this issue? I've found this post (it seems from this particular user), unanswered, all over the internet. I'm having a nearly identical issue and the /only/ error I'm getting is "server error 139" which is not absurdly useful. Thanks in advance, Wes
Reply
Timothy Swiontek responded on 11 Oct 2012 8:00 AM

Server failure 139

Unanswered

You'll be interested to know it's now 10/11/2012 and I'm still scouring the Internet for answers to this question. Good job Microsoft! Great way to provide award winning tech support as usual... *grumbles*.

Reply
Ted Langley responded on 11 Oct 2012 9:19 AM

Server failure 139

Suggested Answer

As with all chages, make a backup of your database before starting this operation.

Try this, delete the register in Store Operations Manager, Database, Register, Register List.  Close Store Operations Manager.  Open back up and recreate the Register 1 again.  

This should fix the problem.

Reply
Jeff @ Check Point Software responded on 12 Oct 2012 5:35 PM
My Badges

Server failure 139

Unanswered

Make sure you are not duplicating the Register number

Make sure RMS is seeing the Reports folder. Make sure that the default printer is not a label printer.

If any OPOS device attached, delete them in the Register settings, exit and come back in and add them one at a time.

Reply
Ryan Nunn responded on 25 Feb 2013 10:15 AM

Server failure 139

Unanswered

Just ran into this last week. Suprisingly we found that is was due to temp files. After deleting all *.tmp files in c:\Doc and Settings\User\Local Settings\Temp\  we were able to successfully launch the POS.

Reply
jdc03 responded on 14 Aug 2017 8:57 AM
My Badges

Server failure 139

Suggested Answer

Just last week I had 2 problems occur that took this one solution to fix.

Initially any Task Pad with pictures as buttons was taking a very long time to load, sometimes over a minute.  Assuming this was a HDD failure incoming, I imaged the drive and swapped it, the problem continued.

The day after the HDD swap, the POS stopped opening all together showing a Server Failure 139 message.  Tried repairing the POS program, tried uninstalling and reinstalling, nothing was working.

Found this thread and decided it wouldn't hurt to try pulling some of the Temp files out and putting them in another folder, incase moving them made it worse.  Took any Temp file from last week and moved it to another folder and the POS started connecting again, but still had trouble loading the Taks Pads with pictures.

Moved any Temp file that was from the past few weeks, when the issue seemed to start, and like magic the Task Pads started loading instantly again!

TL;DR ... if you are getting a Server Failure 139 or your Task Pads are very slow to load when they weren't before, try deleting your temp files back to about the time the problem started.

Reply
Gaby_HQ responded on 16 Oct 2019 3:03 PM

Server failure 139

Unanswered

What I usually  do is make a new windows user and it always fix the problem but for some weeks the it pops back. It's annoying...

Reply
Ted Langley responded on 11 Oct 2012 9:19 AM

Server failure 139

Suggested Answer

As with all chages, make a backup of your database before starting this operation.

Try this, delete the register in Store Operations Manager, Database, Register, Register List.  Close Store Operations Manager.  Open back up and recreate the Register 1 again.  

This should fix the problem.

Reply
jdc03 responded on 14 Aug 2017 8:57 AM
My Badges

Server failure 139

Suggested Answer

Just last week I had 2 problems occur that took this one solution to fix.

Initially any Task Pad with pictures as buttons was taking a very long time to load, sometimes over a minute.  Assuming this was a HDD failure incoming, I imaged the drive and swapped it, the problem continued.

The day after the HDD swap, the POS stopped opening all together showing a Server Failure 139 message.  Tried repairing the POS program, tried uninstalling and reinstalling, nothing was working.

Found this thread and decided it wouldn't hurt to try pulling some of the Temp files out and putting them in another folder, incase moving them made it worse.  Took any Temp file from last week and moved it to another folder and the POS started connecting again, but still had trouble loading the Taks Pads with pictures.

Moved any Temp file that was from the past few weeks, when the issue seemed to start, and like magic the Task Pads started loading instantly again!

TL;DR ... if you are getting a Server Failure 139 or your Task Pads are very slow to load when they weren't before, try deleting your temp files back to about the time the problem started.

Reply

SBX - Two Col Forum

SBX - Migrated JS