[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 317
  • Last Modified:

SQL 6.5 and Docs Open 3.9.5

We are running Docsopen 3.9.5 with SQL 6.5.  MS NetworkAround 9AM this morning, processes began to lock forcing a hard shutdown of one of the document library server.. When it came back up, users could not save a document -- when trying to save getting:

#21 - WARNING - Fatal Error 644
Offending SQL statement is
INSERT INTO DOCSADM.SECURITY (ACCESSRIGHTS, PERSONGROUP, THING) VALUES
(255,0,15500094)

we took the library off lie and are running the DBCC's that normally run at midnight once per week.  They are still running now.

If anyone has experienced something like this and has any insight it would be most appreciated.
0
go4marc
Asked:
go4marc
1 Solution
 
mcmonapCommented:
Hi go4marc,

Can you insert into the database with directly using query analyser?  It sounds as though the issue is a problem with database corruption rather than with the DO config, have the DBCC checks turned up anything?  Since the crash ocurred so early in the day can you feasibly restore a backup.  Obviously you will only lose metadata as the documents that have been changed and created do not need to be restored, only the DB.
0
 
Ken SelviaRetiredCommented:
Sounds like a corrupt index.  DBCC CHECKDB should fix it.  You could also try DBCC CHECKTABLE ('DOCSADM.SECURITY') and DBCC NEWALLOC ('yourdbname')  Have you considered migrating to SQL 2000? DocsOpen is certified on it.
0
 
ScottLordCommented:
DOCS Open on the users PC will not recover from a failed SQL server connection, whatever the reason.  When the server comes back up, the DOCS Open users that did not exit and restart DOCS and any applications will get the above listed error.  Is this your case, or are you having this after the users have stopped and restarted DOCS Open?

Scott
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now