Search results for query: *

Yes we ran the client install on the workstations and they failed the communications test. The server is also failing to communicate to itself when we click the connect button. But I can ping the server from workstations and I can ping the server itself with communication success so I don’t...

We have finally installed Pervasive 7.0 and got away from the w32mkde (single user version) but now we have a problem with database connections. When we look in the logs, it says there isn’t a suitable communication protocol installed. But when you run setup32 and look in the enabled...

We can run one workstation at a time with no problems. The process W32MKDE.exe is running when we are in Macola. If another user (either terminal server or mapped drive) tries to start Macola, it fails with the Mac32up.lbr error, but the W32MKDE process still runs. If everyone is out of...

Thanks to all who helped us in this restore - Status: the restore is up and running after the move back to Pervasive 6x from 7 and a complete initialization and import of all data files. New Issue: Workstation clients are inop - MAC32UP.lbr errors. We have reinstalled the Pervasive client...

We just performed a total restore from backup - the backup contained 1 batch in OE that was selected and invoiced, but not posted. Batch ID 1. I can reprint the invoices (only as duplicates) but the posting operation fails. Is there a method by which we can blow away the batch, reselect, and...

Thanks for the quick response. We were running on an NT server until 3/26. It was locking records and freezing on a regular basis, so we migrated to a windows 2000 server. We are currently running Pervasive 7.0. We were also experiencing BTR errors on the 2000 server, and rebooting on a daily...

Encountered error code 030 on multiple OE files (message 0430). Tried using the Pervasive Rebuild utility, and it claimed that the rebuild was successful and all records were recovered. When I subsequently rebuilt the files in Macola/System/Process/Rebuild, still got the same error code. Also...