ProForm can't find it's databases, an ODBC connectivity test passes, but when ProForm is started, it throws an error. The test system is a small network of Terminal Server and a few Windows 7 machines, a new Windows 7 64 bit machine was installed. ProForm Classic 12.2 is throwing a PFWIN-028 error message, cannot initialize databases. Starting ProForm as Administrator using this registry entry to allow drive mappings to occur works fine, but requires the user to click an extra dialog box on one computer but not the rest of the network.
Today a law firm client called and mentioned they could no longer access Word Document, PDF Files and other network data. After chatting a bit they mentioned that a user saw a window called Crypto Locker which asked for money to restore access on the files.
Recently a client upgraded their ProForm Classic Standard installation from MDB to SQL. They have a terminal Server which wasn't included in the update as only IT people use it. ProForm was coming up saying it could not find a unknown file relating to the databases, the error was PFWIN-028. Looking at the information in odbcad32.exe 32 bit or 64 bit showed no visible issues.
Today's fun call of the day was related to ProTrust having a Ledger locked for editing. The Error (PTWIN-130) is displayed when someone attempts to add a transaction to the ledger. No one knew who or why, but it's been like that for days. There's a right way and a wrong way to fix this particular problem. We'll talk about the wrong way first.
A customer support email box, hosted on Exchange was filling up with messages. A couple a minute for the past 4 days. We have a few Time Warner Road Runner mailboxes setup to forward from one to another, then eventually to an Exchange server. The Scan mailbox forwards to Support, which forwards to the external Exchange support address. The Exchange support mailbox was receiving Delivery Status Notification Failure messages and Undeliverable Attached Image messages a few times a minute. For the past 4 days.
There are things that need checked after converting a database from Access to SQL with SoftPro Standard. I've been through a couple of these, there are things to watch out for. Once the data is converted and with each database showing no unfixed issued during the conversion process, there are some additional items that need done, or checked.