Sorry this is very long, but I've been working on this in my spare time for a few weeks now. There were so many run on sentences that I decide to enumerate in some parts.
My customer has a small store in which they use MS Dynamics POS 2.0. I did RAM and hard drive diagnostics and both are good. There have been no updates (this is on an XP machine.)
I'm assumed that there was something wrong with the program and that we need to reinstall or repair. I posted to this forum and I was advised the database might be full, so I deleted all transactions (which the customer is not upset about - she just wants her 110,000 inventory items to stay!) Still crashed.
The customer found the original discs and packaging for the software.
1. First I tried a repair. Still crashing.
2. After removing all elements, except the database itself, the software kept crashing.
3. I started over removing all elements including SQL Server and all it's components. But I ran into a problem I will describe in step 7 because I could not solve this on a Friday night (given that it seems to take a business day or two to get an answer and I wanted to get this PC back by last Monday.)
I had done hardware diagnostics before I began fooling with the software. There was no indication of problems. However, after reinstalling the software, it seemed the problem might possibly be hardware related.
4. I put back the image of the original drive and then I changed out the DDR2 memory doubling it from 1 GB to 2 GB's. Still crashing.
5. I then decided to run SpinRite on the drive. It did in fact get stuck for many hours on part of the drive. I purchased a new drive and put the image on it. Still crashing.
6. I noticed there was an error message on the motherboard during startup related to overclocking. So I took the drive and put it in another PC (and Activated XP again.) Still crashing!
7. So I:
a. removed all components of the program and database
b. reinstalled MS Dynamics
c. set up a blank database
d. ran the restore database process (restore successful)
e. closed the database and restarted
f. attempted to "change database connection".
I've run into the following errors (pics included):
"Could not connect to the database. Make sure you type the correct name. Also, make sure the computer that has the database is available and that the port you specify is the correct one."
I assume the port is still 1976. I remamed the MPOS Instance to MPOS2 on the recovered db. Any ideas???
*This post is locked for comments
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,782 Super User 2024 Season 2
Martin Dráb 229,067 Most Valuable Professional
nmaenpaa 101,150