Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Highlighted
Michal Kovacik
Frequent Visitor

Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

I am getting the error shown in attachment when trying to display case log.

My suspicion is that it is generated due to memory leaks in MS Java VM (or SD client itself) as it appears after about 2-3 days of use of the computer with OVSD client running (and just for tickets with long case logs). In "About..." box I found following:

Java Vendor: Microsoft Corp.
Java Version: 1.1.4
Free VM Memory: 55736 Bytes
Total VM Memory: 45749238 Bytes
Used VM Memory: 45694414 Bytes

OVSD client version is:
hp OpenView service desk 4.5.0588.4913 (SP49) Mathilde 10r2 HF
Using hotfix
for build: 4913
number: 0003

I looked at this by one of my colleagues and he had more free VM memory.

Does anyone please have any advice? I know only one workaround for this and it is reboot - but I want to avoid it as much as possible because loading all the stuff I need for the work lasts too long and involves too much password-typing...
5 REPLIES
Vasily Kamenev
Honored Contributor

Re: Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Hi
Close the client, clear the %APPDATA%\Hewlett-Packard\OpenView\Service Desk\cache folde from any files, and delete all .dat files from folder %APPDATA%\Hewlett-Packard\OpenView\Service Desk. Run client. Try catch the error. If error come with form - problem in "Form", try use another form, if error come whem change one of the field - problem in field, try to do the same on other SC, if no problem, the problem in SC.

Vasily
Michal Kovacik
Frequent Visitor

Re: Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Hello,

Thanks for the advice, but these steps have already been advised to me by my colleagues and did not help.

However, I discovered that this is probably related to Windows (not just Java) having too few free system resources (window handles&co., as when too many applications are open, also some other programs fail to open a new window).

In SD client log I found following errors (more occurences of these two):

====================================
Å t, 14/08/2008 16:33:32 com.ms.wfc.core.WFCWin32Exception: The operation completed successfully
at com/ms/wfc/app/Window.createHandle
at com/ms/wfc/ui/Control.createHandle
at com/ms/wfc/ui/Edit.createHandle
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.setVisible
at com/ms/wfc/ui/TabControl.updateTabSelection
at com/ms/wfc/ui/TabBase.onSelectedIndexChanged
at com/ms/wfc/ui/TabBase.wmSelChange
at com/ms/wfc/ui/TabBase.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.SendMessage
at com/ms/wfc/ui/Control.sendMessage
at com/ms/wfc/ui/Control.reflectMessage
at com/ms/wfc/ui/Control.wmNotify
at com/ms/wfc/ui/Control.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.CallWindowProc
at com/ms/wfc/app/Window.defWndProc
at com/ms/wfc/ui/Control$ControlWindow.defWndProc
at com/ms/wfc/ui/Control.defWndProc
at com/ms/wfc/ui/Control.wmMouseDown
at com/ms/wfc/ui/Control.wndProc
at com/ms/wfc/ui/TabBase.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.DispatchMessage
at com/ms/wfc/app/Application$ThreadContext.runMessageLoop
at com/ms/wfc/app/Application.run
at com/hp/ifc/ui/AppConsole.main

Å t, 14/08/2008 16:33:39 com.ms.wfc.core.WFCWin32Exception: Not enough storage is available to process this command
at com/ms/wfc/app/Window.createHandle
at com/ms/wfc/ui/Control.createHandle
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.createControl
at com/ms/wfc/ui/Control.setVisible
at com/ms/wfc/ui/TabControl.updateTabSelection
at com/ms/wfc/ui/TabBase.onSelectedIndexChanged
at com/ms/wfc/ui/TabBase.wmSelChange
at com/ms/wfc/ui/TabBase.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.SendMessage
at com/ms/wfc/ui/Control.sendMessage
at com/ms/wfc/ui/Control.reflectMessage
at com/ms/wfc/ui/Control.wmNotify
at com/ms/wfc/ui/Control.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.CallWindowProc
at com/ms/wfc/app/Window.defWndProc
at com/ms/wfc/ui/Control$ControlWindow.defWndProc
at com/ms/wfc/ui/Control.defWndProc
at com/ms/wfc/ui/Control.wmMouseDown
at com/ms/wfc/ui/Control.wndProc
at com/ms/wfc/ui/TabBase.wndProc
at com/ms/wfc/ui/Control$ControlWindow.wndProc
at com/ms/wfc/app/Window.callback
at com/ms/wfc/win32/Windows.DispatchMessage
at com/ms/wfc/app/Application$ThreadContext.runMessageLoop
at com/ms/wfc/app/Application.run
at com/hp/ifc/ui/AppConsole.main

==================================

Does please anyone know how to increase available system resources (Win XP SP2) to avoid such issues? In my work it is essential to have a high number of applications running at once...



Vasily Kamenev
Honored Contributor

Re: Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Hi
You can use the new client 2008, this client having on init properties used memory value.

Vasily
Rajesh Nair
Esteemed Contributor

Re: Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Hi,

Locate the file mdac.inf in the folder c:\windows\inf (this is a hidden folder). Press the right mouse button while selecting the file mdac.inf, and select install. After installing, re-boot the machine. This should replace the existing MDAC with the appropriate one for the environment.

Regards

Rajesh
Michal Kovacik
Frequent Visitor

Re: Getting error "com.ms.wfc.core.WFCException:" in SD client 4.5

Thanks for advices, I'll try them when I have time to reboot the PC - I have a workaround for the issue - when keeping the number of running programs (open windows) as low as possible, it does not appear - it is definitely related to system resources.
//Add this to "OnDomLoad" event