It's all set now. I just had to change all the permissions proper and chmod a few things. restoring from tape to a different folder a few small representative files in each share did the trick for me.
It must be my conf, but testparm comes out fine with no errors (I even fixed the ulimit warning). Please help me, this must be up by Monday! I'm running 3.5.1 now, or trying to, but was running 3.4.x on suse 10.1 (now I'm on opensuse 11.2).
If the interfaces line is changed to "eth0, eth1, lo"...
I have an opportunity to finally troubleshoot this terrible issue. We have, at least 3 times a week, a problem where our pervasive db goes into a bad state and gives our Max users all kinds of errors until we restart the db services on the Windows 2000 server running Pervasive 8.7 sp3 (as are...
I have a project table, 3 types of project costs (PO, expenses or non-PO, and hours) there is also a rate table for hours and department (which I had to do for security when entering data).
Below (after my ramblings) is my current sql madness. Hopefully it's spaced well enough to be readable...
same error on both, 171. the file.ddf in the max data directory is what I've been trying, and what's necessary for the max client to work.
I restarted the transactional service on the server but it didn't seem to help. Same errors, etc.
I figured out the PSA utility, it was free on Pervasive's site. I used the same paths as the installer does and the relational tests work just fine, as does the TCP/IP test, but the transactional tests fail after initialize (and pass on clean up) with that 171 error.
This happens after...
Ok, changing the client settings on the max server in PCC from "Workstation only" to "try server first then workstation" allows me to open the file.ddf in the function executor.
AND the Max client now works on the server. So that was a configuration issue there.
Why the heck is it happening on...
this workstation (named "deploy") shares a folder on the network (one we use for sharing isos we've backed up) as well as a shared folder for Kaspersky administration kit remote installs. I can browse both folders properly on other workstations when I type \\deploy in explorer. So IPC$ on my...
I tried the function executor to open a btrieve dat file and no luck, same 171 error. Ditto for file.ddf and this was opening the file through unc.
I have the same trouble whether I try unc or a mapped drive letter when using crystal.
Using just ODBC in crystal works fine. Unfortunately the Max...
I shouldn't have to reboot the server for a new odbc connection if the connection tests ok. That's crazy talk.
Besides, most other clients in the office are fine, I'm trying to troubleshoot this one.
I'm sure it's to do with this issue of ddf... I tried creating a new crystal report and...
On the workstation in question, I can read and write data just fine in Pervasive SQL Data Manager.
I tried reinstalling the pervasive 8.7sp3 client and when it got to the analyzer, I had it run all tests. The transactional tests fail 171. This is on a reinstall! I have that analyzer still open...
if I can fix this 171 error, I can be stable again, for now.
As for the server, I'm thinking it's a configuration issue with the pervasive client settings... please review and let me know why crystal would fail with 3012:
Windows Registry Editor Version 5.00...
8.70.14.0 is the version on both the server and the clients.
PCC lets me in just fine when I use it on the server and when I use it on the workstation in question. The DSN checks out.
When I try to run a crystal report tho, it fails.
When I try to run it on the server, it fails with that 3012...
ok, I cannot open the Max client on the server, nor can I on a critical workstation that runs CRD. Further, I can't run crystal reports that use btrieve either from both machines.
The workstation shows file cannot be opened, while the server shows btrieve error 3012... it's like I don't have the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.