-Is your Citrix environment result of a migration from 4.0?

-Can you run a dscheck.

-Can you paste the relevent part of the log file in here? (my documents)

Yes, Citrix was migrated from 4.0.

PS ist the advanced edition.

dscheck show this:

-----

Data Store Validation Utility.    Version: 6.23

Can't read package info from data store.
Can't read package info from data store.
Can't read package info from data store.
Finished data store validation.

-----

And this ist the log file:

-----

15.07.2008 10:31:20 -- _____________________________________________________________________________________
15.07.2008 10:31:20 -- Published Applications Utility version 4.5.1.6 Build: 504 is starting.
15.07.2008 10:31:21 -- This version of PAU is not licensed, get a license at www.gourami.eu
15.07.2008 10:31:21 -- Busy finding a citrix environment...
15.07.2008 10:31:21 -- √ Farm object succesfully created
15.07.2008 10:31:21 -- √ Connected to Container-Terminal
15.07.2008 10:31:21 -- √ You are Citrix Administrator.
15.07.2008 10:31:22 -- √ Found server: TS7
15.07.2008 10:31:22 -- √ Found server: TS6
15.07.2008 10:31:22 -- √ Found server: TS-MAIN
15.07.2008 10:31:22 -- √ Found server: TS-CMS
15.07.2008 10:31:22 -- √ Found server: TS1
15.07.2008 10:31:22 -- √ Found server: TS4
15.07.2008 10:31:22 -- √ Found server: TS5
15.07.2008 10:31:22 -- √ Found server: TS2
15.07.2008 10:31:22 -- √ Found server: TS-APP2
15.07.2008 10:31:22 -- √ Found server: TS3
15.07.2008 10:31:22 -- √ Found server: TS-APP1
 

-----

There are some known issue's with MFCOM on migrated farms. The old migrated published applications are probally causing the troubles.

Here's a way to find them:

Get dsview.exe, it comes with your Citrix CD and enables you to view the datastore on low level.
 
Start the tool, go to the tab 'directory', 'serverneighborhoods', expand your farm name, and expand 'MFapps', 'MFApps_obj'. I think you can probally see a irregular patern in some of the codes associated with your apps.

If you create a new published application, you see code assosiated with this applications.

Applications with totaly different code paterns are probally the onces migrated.

Thanks for the hint, PAU is working!

There was several apps with irregular pattern and one app with corrupt properties.

First of all great that your problem is solved.

Can you please specify in detail what was wrong and how you solved it?, some other users also had this problem, maybe you can provide these other people with a solution!

What corrupt properties exactly?

Here are some details:

1. Several apps in Citrix DS View had shown irregular patten like "3554-0009-000e6fb3[MfappObjectClass5][2748939] (Windows Explorer)", with only 7 digits at the 3rd value. The correct/recreated app shows like "3554-0009-000e6fb3[MfappObjectClass5][3379921e2] (Windows Explorer), with 8 digits.

2. Some apps had corruped properties like no "command line" and "working directory". The AMC shows a warning if you try to edit the properties.

Hi
We are having the same issue but we have not migrated our citrix farms so i am not 100% sure if this issue is relevent or not but what i could say PAU worked with out any issue and this has now become an recient issue.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at MetaFrameCOM.IMetaFrameApplication5.get_DistinguishedName()
at PAU.Form1.ConnectToFarm()
at PAU.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PAU
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///C:/Program%20Files/Gourami/PAU45/PAU.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/Sy...
----------------------------------------
zip
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files/Gourami/PAU45/zip.DLL
----------------------------------------
PAU
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///C:/Program%20Files/Gourami/PAU45/PAU.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f...
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5...
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d...
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b7...
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5...
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e08...
----------------------------------------
Interop.MetaFrameCOM
Assembly Version: 5.0.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///C:/Program%20Files/Gourami/PAU45/PAU.exe
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d...
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Can you paste the dsview with a open view on the applications tab?

Hi

i have launched DsView and i only see 4 Tabs. Directory, LHC, ContextIds and UIDs

read this reply carefully: Submitted by Gourami Support on 15 July, 2008 - 13:28.