Quantcast
Viewing all articles
Browse latest Browse all 209

prim24375:Receiving an “Event Code: CIIUB-3936-B Message: Connection is in use by another statement.” after waiting to save a layout.

Solution ID: prim24375
Receiving an "Event Code: CIIUB-3936-B Message: Connection is in use by another statement." after waiting to save a layout.
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Receiving an “Event Code: CIIUB-3936-B Message: Connection is in use by another statement.” after waiting to save a layout.
Problem: Receiving the following error when attempting  to ‘save’ a layout as a global layout.

The ‘save’ action does not complete for 10 minutes, after which time the error below is generated:


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          18-Mar-05

Executable:    PM.exe
Application:   Primavera Project Manager
Event Code:    CIIUB-3936-B
Message:      
  Connection is in use by another statement.

Context:
  1: TfrmMain.actFileOpenExecute
  2: TCFormManager.SetToolbar
  3: TfrmLogin.FormCreate
  4:
  5:
  6:
  7:
  8:
  9:
  10:

Detail:
  Type:        EDBEngineError
  Object Type: TTimer

Database Error:
1: Connection is in use by another statement.
   Category:          42
   Error Code:        10771
   Sub Error Code :   19
   Server Error Code: 0


Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0350.0005.0004.0001
IMG: IMG Win32 #1000

System Info
===========
Username: assmith   Hostname: BBTSRVMDS37
OS Version: Windows NT ver 5.0, build 2195, Service Pack 3 (Intel Pentium)
BDE Version: 500 (1901-5-11) OTHER
BDE Ini file: C:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

Cause: There may be a variety of causes.
e.g. a corrupted layout means the layout never completes the save thus maintaining a connection to the database.
Therefore an error is generated at some stage when a second connection is made to the database.

The Connection in use appears to be a secondary error not the primary cause of the application failure.

Fix:

To prevent the error:



  1. Open the ‘Classic Schedule’ layout

  2. Use the ‘Save As’ to create a new layout.

  3. Tailor the layout as required.

  4. Delete the original layout which is corrupted.

Viewing all articles
Browse latest Browse all 209

Trending Articles