HMI Service Failed
Even I had same problem while I was working on SE. My DB was sql. But this sipmle trick will solve the problm. No need to uninstall any software..
[FONT="]68481 - HMI Server Services Fail to Load in FactoryTalk View Studio[/FONT]
[FONT="]Problem[/FONT]
One of the following error messages appears when trying to open an application in FactoryTalk View Studio:
- Failed to load HMI Server service[FONT="][/FONT]
- Cannot connect to addin object, Name: Application Handler, Cause: 80042089[FONT="][/FONT]
- Server verification has failed,[FONT="][/FONT]
- Studio may hang on opening (while loading services)[FONT="][/FONT]
- Failed to instantiate service[FONT="][/FONT]
- Failed to load data server rshmi.tag server[FONT="][/FONT]
- [FONT="]Failed to initiate the service RSHmi.HmiDlgReadservice.1[/FONT]
The following error message appears when creating new local (standalone) or network (distributed) application
- Failed to instantiate HMI Server[FONT="][/FONT]
- Failed to initiate the service hmi.derivedtags.1[FONT="][/FONT]
Alternately, Studio may hang on opening (at around 70%) without any error message.
This behavior is observed on a busy system, typically a laptop, that is simultaneously running services associated with various software applications ranging from:
- [FONT="]Third party VPN services[/FONT]
- [FONT="]iPod services[/FONT]
- [FONT="]CAD software[/FONT]
- [FONT="]a variety of third party HMI software, such as: [/FONT]
- [FONT="]iFix[/FONT]
- [FONT="]Siemens[/FONT]
- [FONT="]Wonderware, and etc.[/FONT]
In addition, the following error message has also been seen in association with the root cause described below:
Cannot connect to addin object[FONT="]
Name: Application Handler
Cause: 80042089[/FONT]
[FONT="]Environment[/FONT]
- [FONT="]Microsoft Windows XP Professional[/FONT]
- [FONT="]Microsoft Windows Server 2003 Standard Edition[/FONT]
- [FONT="]FactoryTalk View SE 5.x[/FONT]
- [FONT="]FactoryTalk View ME 5.x[/FONT]
[FONT="]Solution[/FONT]
Warning - This solution only applies to Windows 2000, Windows XP and Windows 2003 Server. Do not apply this to any other operating system. Doing so could cause the computer to become non-operational.
The behavior is caused by the system running out of so-called desktop heap. Aside from a visible desktop that hosts windows, menus, hooks strings, etc. there are also invisible desktops running under non-interactive Windows stations. These can be thought of as a collection of desktops associated with different processes.
All Rockwell services, and there are a number of them, run under LocalSystem account and that the checkbox
Allow Service to Interact with the Desktop is not checked.
As such, Rockwell services require desktop memory from the special section of the desktop heap memory which is limited to 48Mb. The memory from this pool is assigned to the requesting non-interactive services in 512Kb portions by default.
However, the system-wide buffer of 48Mb is also serving other types of third party services:
- [FONT="]Some services may also be running under LocalSystem.[/FONT]
- [FONT="]Some may be running under different user account context and with services being allowed to Interact with the Desktop.[/FONT]
On a busy machines, the total desktop heap might be exhausted prematurely, before Rockwell (non-interactive services) has a chance to allocate required desktop heap for their own needs.
[FONT="]Desktop Heap Allocation in the Registry[/FONT]
The size of each desktop heap allocation is controlled by the following registry value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
[FONT="]Default Registry Value[/FONT]
The default data for this registry value will look something like the following (all on one line):
%SystemRoot%\system32\csrss.exe[FONT="]
ObjectDirectory=\WindowsSharedSection=1024,3072,
[FONT="]512[/FONT]
Windows=On SubSystemType=WindowsServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=OffMaxRequestThreads=16[/FONT]
The solution is to modify the
SharedSection value (highlighted in the registry key above) by increasing its third value (highlighted in blue) from
512 to
1024. The modification has been already included in the attached registry key. After the registry is applied, a reboot is mandatory.
[FONT="]References[/FONT]
http://support.microsoft.com/?id=184802
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
File Attachments
Thanks,
Mrunali