A call to an OS function failed

[JDietz]

Hello!

We're using 5.1.6.747 on a Windows 2003 Enterprise Edt. If we are working with PLSQLDeveloper on a terminal server session (remote desktop session) on that server (client is XP) we are often getting the error "A call to an OS function failed" when we change back to the XP desktop and the return to the remote session again. First it seemed that PLSQLDeveloper has just freezed but we found out that PLSQLDeveloper popped up a messagebox in the background with that error. Using ALT-TAB brings the message box to the top and we can choose OK. Doing so allows us to continue our work in PLSQLDeveloper like there was no error.

Do you have any ideas how to prevent that pesky error?

Here's a debug output:
---------------------------------------------

PL/SQL Developer 5.1.6.747 02.8096 - Unlimited user license
C:\Program Files\PLSQL Developer\PLSQLDev.exe

28.04.2004 08:32:33 Application started
28.04.2004 08:32:38 SetSessionAction starts: Main session
28.04.2004 08:32:38 SetSessionAction ends
28.04.2004 08:32:38 ExecuteConnectScript starts
28.04.2004 08:32:38 ExecuteConnectScript ends
28.04.2004 08:32:38 SessionChanged
OracleHomeKey: SOFTWARE\ORACLE\HOME0
OracleHomeDir: c:\oracle\ora81
Found: oci.dll
Using: c:\oracle\ora81\bin\oci.dll
28.04.2004 08:33:08 AddPlugInPopups Start 1
28.04.2004 08:33:08 Version Control Interface 1.0
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 ProcedureWindow
28.04.2004 08:33:08 SQLWindow
28.04.2004 08:33:08 TestWindow
28.04.2004 08:33:08 CommandWindow
28.04.2004 08:33:08 AddPlugInPopups End
28.04.2004 08:33:09 Create TProcEditForm
28.04.2004 08:33:09 ProcEditForm.GetTabNames
28.04.2004 08:33:09 + InstallAMS
28.04.2004 08:33:09 ProcEditForm.GetTabNames done
28.04.2004 08:33:10 ProcEditForm.GetTabNames
28.04.2004 08:33:10 + InstallAMS
28.04.2004 08:33:10 + InstallAMS
28.04.2004 08:33:10 ProcEditForm.GetTabNames done
28.04.2004 08:33:18 Exception: A call to an OS function failed

Regards,
J. Dietz
Witron GmbH

 

[Marco Kalter]

I noticed some "+InstallAMS" messages in the logfile, which are unknown to me. Are you perhaps using some 3rd party Plug-In? If so, does it help if you disable this Plug-In (or Plug-Ins)?

 

[JDietz]

Hello,

"InstallAMS" is just the name of some package I opened with "view".
so this could not be the reason.
but I found out something very interesting:
the messagebox only pops up if you have a package(spec or body) or similar other "program window" open in edit or view mode. If you set the focus to the "browser" sidebar you can switch back to the XP desktop and fourth to the terminal session without getting any troubles BUT if you set the focus into the program window then you will receive that error when MINIMIZING the terminal session window on the local XP desktop. after restoring/maximizing the terminal session window you can see a flickering pop up that immediately hides behind the PLSQLdeveloper window.
So this definetely has something todo with the program window and Windows 2003 terminal server. Setting the focus to a command or sql window and then minimizing the session on the local XP desktop does not cause that error.

Have you the possibilities to reproduce that error using windows 2003 and a XP terminal server session?
We get the same error from each of our Windows 2003 terminal servers.

cheers,
J

 

[Marco Kalter]

We have created a PL/SQL Developer patch that will log this particular error, so that we can find the exact cause. I will upload it shortly and will send you a notification by e-mail.

 

[J. Cooper]

I see the same thing in 5.1.4.730, but our Oracle server is on an NT4.0 box. However, I think that our domain controller and directory server has been upgraded to Win2003 Server, as I have previously done this (in the last week or so).

Hopefully that's some helpful information. I'd appreciate notification of the patch also.

John Cooper
NewEnergy Associates

 

[Marco Kalter]

If you send me an e-mail, I will send you the patch.

 

[J. Cooper]

I did get the patch, but never got around to deploying it. However, v6.0 appears to have resolved the problem. Thanks!

 

[Marco Kalter]

Okay, thanks for letting me know.