SOS! only c/dart can help us??

Suok

Hi all,
NAV 4.0 SP3, native server

The problem is that the database has locked and no one can login (to make backup or to do something). While trying to open the database the following message apperas:

Other concurrent activities have reused the available space in the database that contained your snapshot of data. This can occur in connection with time-consuming tasks such as printing or making backups. Wait until there are fewer concurrent updates of the database and try again.
...
(probably you know the other part of the message)

We have studied the previous posts of this forum regarding this problem, but all the advices do not help us. We can not open our database neither in ordinary mode nor on readonly mode (with dbreadonly=yes).

http://mibuso.com/forum/viewtopic.php?f=23&t=13560&start=0&hilit=Other+concurrent+activities+have+reused+the+available+space+in+the+database+that+contained+your+snapshot+of+data

This topic tells us to use c/dart... Has anything changed since 2006? Is c/dart the only way to restore our database?

Thanks in advance

matttrax

Why not restore from the last backup? Or is this another case where backups are not being made on a normal schedule?

bbrown

Well since version 4 is no longer supported would MS even offer the service? I understand that C/Dart does not work with newer versions (5.0 and up?). So is MS even keeping it around?

kylehardin

%Other concurrent activities have reused the available space in the database that contained your snapshot of data

This usually means that the database is very close to being full, meaning there isn't enough space inside the FDB file to allocate for the internal equivalent of a transaction log. You won't see that space allocated if you do File, Database, Info - it only gets allocated during transactions. But File, Database, Info will probably show that your database is almost full.

However - if you are locked out,that is another problem. You could try stopping and restarting the database service (let it shut down cleanly!), which will force a rollback of whatever transaction is taking the space. Once that is restarted, users should be able to get back in, and you can take a look at the database size under Info.

The "permanent" fix is to expand the database size so it has adequate transaction working space.

Alex_Chow

I think your only option is to call Microsoft and ask them what to do.

I hope you're still current on the annual enhancement plan...

themave

Try as suggested, shutting down the server, it rebuilds it when first opened, and you should be able to log in and expand the database.

Suok

Thank you all for your replies!

For us the easiest and the cheepest way was to restore backup. In this case we partialy lost data for several hours and it was not critical for business.
Shutting down the server did not help us, because when this problem was transferred to us the users had already restarted the server without correct exit. We tried to restart it correctly, but there was no result.
The customer is not signed for annual enhancement plan, so we decided not to refer to Microsoft.
Thank you all for your help!