Hello,

Just heard of this Forum and i thought i'd chime in. (Maybe i can finally resolve my issues.) We have the Pervasive C/S with seven sub-500MB Address Books on a single 3GHz P4 server. It runs Windows 2000 Server and has 1GB of RAM. All of my clients have SR3 and most are using XP with a few older 2k machines. No remotes, no FTP stuff.

I have an issue where for some reason the ntdbsmgr.exe process simply dies. Nothing is written to the event log. That process is what controls the SQL portion of the Pervasive database. There are two Pervasive Services, and restarting those doesn't seem to help. The only remedy has been to restart the server entirely. I have also noticed that the process doesn't seem to deflate the way i'd exect it to. It just swells up to about 300MB and stays there.

I also get this occasional popup error, which writes the following to the App Event Log....
Application popup: EmailService.exe - Application Error : The instruction at "0x77f88216" referenced memory t "0x00000010". The memory could not be "written".

We have support contract, and i've been through it with Maximizer's people but we haven't fixed it. The server's only other responsibility is Yosemite Backup, which runs in the early AM hours when nobody's here. It has a 10k SCSI drive and IIS is off.

I've tried backup/restore of the ABs and disabling or uninstalling what i can. I have not tried a complete reinstallation. I am also testing the SQL version, but moving to that would be a gigantic job.

Other than this, Maximizer has been "fairly" reliable in the three months I've worked here. Don't get me wrong, i've grown to loathe Pervasive and Max is incredibly slow, but as long as its running i'm happy.

But, someday i'm going to need to take a day off, and won't be here to babysit the server. Any ideas that anybody has would be great.


-jim guthrie

Did you setup the email service to be able to talk to a real SMTP server? We missed that at one point and had the same issue.
For us, the configuration of an SMTP server seemed to resolve it.

I am having the same trouble. The exact same errors. I am lost on what to do. Did you find a resolution? I had to stop SMTP service on my machine. WE had to configure it to work with Argosoft did you?

Thanks Leslie

We experience the same problems, although we have our own Exchange and did setup the SMTP e-mail on Maximizer server. The message pops-up about every 2-8 hours. Seems not to bother anything though but it's annoying. I suspect it has something to do with Campaign Manager.

We did decide to upgrade from Pervasive to MS SQL (although more expensive) because we feel it's more secure (allows folder lockup, which Pervasive doesn't - big security risk!).
-- Rudy K., Canada

I did fix the e-mail service to talk to the correct SMTP server. I had an issue where the Address Book ID was "0", and Maximizer hates that so it wouldn't let me click any of the other tabs. I changed it to "1" and it was fine. (Maximizer's suggestion that recreating the AB didn't work.)

Our crashes seem to be much less frequent than they used to be, but it still happens. The last two were because I tried to open the Notes table in PCC to see what's in there. (I want to export my notes to per-company text files.)

My SMTP server is different than my Maximizer server, so my service was never started. I'd never want Maximizer to run along side of anything if I could avoid it.

The truth is that we're migrating away from Maximizer for this particular application, so if I can keep it the way it is right now I'll be happy. Obviously I'm not going to spend the time and money to research SQL more than I already have. I was never able to figure out what makes ntdbsmgr.exe crash. Oh well.