[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Write Failed (OpenInsight Specific) ====
=== At 19 OCT 1999 02:49:47AM Michael - LMS wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
I have OI 3.7 and have a situation where a WRITE failed.  The Get_Status function returned zero and @FILE_ERROR had the following values:

 - 1013

 - K:\REM_AVEN\DATA\FIN\REV28119.LK

 - 72



What is the error 1013 and where can I find out what it means.



Thanks,

Michael
</QUOTE>
----

=== At 19 OCT 1999 09:30AM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:  ===

<QUOTE>from the REVERROR.DAT file, this is

FS1013:   Group lock timeout error.



So try increasing the group lock timout value in the REVPARAM file.





akaplan@sprezzatura.com

[url=http://www.sprezzatura.com]Sprezzatura Group[/url]

[img]http://www.sprezzatura.com/zz.jpg[/img]

</QUOTE>

----

=== At 19 OCT 1999 10:58PM Michael - LMS wrote:  ===

<QUOTE>Thanks Aaron,



I tried your suggestion and created a REVPARAM file in the appropriate directory and set the GoupLockTimeOut variable to 180 (The default is 60 I believe).  This did not fix the problem however.



If I try running the routine on a machine that has encountered this problem it causes the PC to freeze and pressing  shows that the OENGINE is not responding.



If I try running the routine on a machine that has not encountered this problem before then it stops at my debug statement that I put in the code and returns an error message saying it was unable to write the record.



Any other suggestions???



Thanks,

Michael

</QUOTE>

----

=== At 23 JUL 2001 01:49AM Matt Crozier wrote:  ===

<QUOTE>I found exactly this problem when locks were not being removed in an update loop.  Under some circumstances, the Unlock command was not being processed correctly because the @id variable it was using had been cleared by another (error logging) process.  The locks built up and, hey presto! - FS1013.



Hope this helps anyone else who encounters this same problem.

Cheers, M@

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=7C87B1AB313951E98525680F00258491|View this thread on the  forum...]]