ntdbsmgr.exe causes cpu 100 percent

[chrism1]

We just recently started experiencing an issue with our Pervasive SQL 2000/Macola 7 installation.

ntbdsmgr.exe will cause 100 percent utilization on our nt4 server.

Like I said, it just started happening so I'm going through "whats changed?". Wondering if anybody has a heads up on this.

Thanks

 

[kscheeler]

I've had that issue with some of my clients on the same setup where if the pervasive session gets ended abruptly, like going into the pervasive monitor and ending a user's session will cause that. The only remedy seems to be to restart the server.

I don't see it as much if you rebooted a workstation that was logged into Macola but definitely through the pervasive monitor.

Typically, only admin users have rights to it because you have to log in to the server to access it.

Kevin Scheeler

 

[crystalreporting]

From memory, this was an acknowledged problem in 7.6.200..

Peter Shirley

http://www.linkcorp.com

 

[dgillz]

Chris,

How long have you been on 7.6.200? Hs this just started? Peter may have something here.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[chrism1]

Don

I upgraded a few months ago at this site. The problem has started in the last week or so. So far it has occurred at night (no events) and I catch it in the morn. Still digging.

Chris

 

[crystalreporting]

Check out thread318-828454 on the Pervasive forum.

Peter Shirley

http://www.linkcorp.com

 

[maccrystal]

Check the service pack level for PSQL200i. You should be on SP4.

http://www.appstratinc.com

 

[chrism1]

I lied on the no events....I checked the psql logs and I have pinpointed the time when it hangs. So the possibilities are narrowed to backup (Backup Exec) or a scheduled Visual Cut report or both.

In any case it seems I'm a bit behind the times. I checked the version on the dll's and we are running 7.82.

Thanks for all the help.

 

[maccrystal]

You need to check the build level. SP4 is build 7.94.251 on Novell, and build 251 on Windows. service pack 4 has some changes that may resolve you high utilization problem. You can also revist the report visual cut is running and check or change the joins. Installing SP 3 will require you to update all workstations.

SP3 must be installed before applying SP4. SP4 is for the engines only and does not require a workstation update. You may also see a speed improvement on SP4 if you are using ODBC connections instead of Native Btrieve through crystal.

http://www.appstratinc.com

 

[chrism1]

I moved the suspect scheduled Visual Cut report to another time and the problem went away -- probably a conflict with the nightly backup.