RMS Crashes and Invoice is lost

Hi Sid,

There are lot of thing that the pos could crash. Hardware devices, database connection, corrupt installation, etc. The next time your POS crashes, could you right click my computer then select Manage. Expand the folder Event Viewer, click on Application. Check if there are any errors.

Additional questions:

1. How many register computer do you have?
2. Is the register computer separated from where the database is located?
3. If you have other register, does this issue occurs on a different register?
4. What are devices installed in you register computer?
5. What Operating System do you have in your register machine?

We'll be waiting for your update

Try> Hi

##-----------------------------------------------## Newsgroup Access Courtesy

In answer to your Questions

1. 1 X POS and 1 x Back Office
2. No the register is the Sql Server so it's not like it is having to connect to the Database across a Network

H> Hi Sid,

Jeff

Sorry -- the Version is RMS 2.0

Thanks for the reply -- i'll give this a go.

Sid

"Jeff @ Check Po> Sid,

Native Client Configuration on the left | double click Client Protocols | make sure that Named Pipes is enabled | right click on Named Pipes and select Order | change so the order is 2 if Shared Memory is #1, TCP/IP should be #3 | close

Configuration | Surface Area Configuration for Services and Connections | select Remote Connections on the left | make sure that Local & Remote connections and Using both TCP/IP and Named Pipes is selected | close this screen Select Surface Area Configuration for Features | select Enable OPENROWSET and ... | close entirely

Network Utility | move TCP/IP and Named Pipes to the right hand box, making sure that Named Pipes is on top | select the Alias tab | Add button | put either the computer name of the database server machine or the IP address of the server machine | close (The database server machine should always have a static IP address, that's another post)

Hi Sid, I am curious if changing the configuration resolved your issue? We were battling this in the past with specific devices and managed to get it resolved, including checking the SQL config suggested by Jeff, but wanted to know if that was THE fix or if it was something else we did.

Thanks!

Brand> Jeff

SQL Native Client Configuration on the left | double click Client Protocols | make sure that Named Pipes is enabled | right click on Named Pipes and select Order | change so the order is 2 if Shared Memory is #1, TCP/IP should be #3 | close

Configuration | Surface Area Configuration for Services and Connections | select Remote Connections on the left | make sure that Local & Remote connections and Using both TCP/IP and Named Pipes is selected | close this screen Select Surface Area Configuration for Features | select Enable OPENROWSET and ... | close entirely

Client Network Utility | move TCP/IP and Named Pipes to the right hand box, making sure that Named Pipes is on top | select the Alias tab | Add button | put either the computer name of the database server machine or the IP address of the server machine | close (The database server machine should always have a static IP address, that's another post)