Problems with packaging Exact Globe 400.433
-
Wednesday, November 09, 2011 11:14 AM
Anybody has experience with sequencing this application ?
Situation: packaged as normal app, get these messages:
----------------------------------------------------------
The Sequencer detected an unsupported driver. Kernel and user-mode drivers are not supported in the App-V virtual environment.
The unsupported drivers detected are as follows:
SYSTEM\CurrentControlSet\services\MQAC
Extract or obtain the standalone driver and install it locally on the client.
------------------------------------
The Sequencer detected a printer driver. Printer drivers are not supported in the App-V virtual environment.
The printer drivers detected are as follows:
novaPDF 7 Printer Driver
Extract or obtain the standalone driver and install it locally on the client.
=================================================
When I start the app Exact globe on the client following message;
=============================================
I thought i was because the app needs WORd and EXCEL. so I edited the OSD of Exact Globe with the codebases
of WORD and EXCEL in it. But still not working.
Can somebody give me a little hand with it ?
Gr. pvds
All Replies
-
Wednesday, November 09, 2011 1:01 PMModerator
Drivers (kernel, user-mode, printers etc) can't be sequenced. As outlined in by the messages from the Sequencer, package these separately and install them to clients that will run the virtual application.
Does the automation error message occur if the application is installed instead of virtualized? Have you use Process Monitor to get an understanding of what's happening at the time of the error?
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.- Proposed As Answer by Aaron.ParkerMVP, Moderator Monday, November 14, 2011 11:37 AM
- Marked As Answer by Aaron.ParkerMVP, Moderator Sunday, January 08, 2012 10:22 PM
-
Wednesday, November 09, 2011 1:27 PM
Hi AAaron,
OK i'll do that, you mean packaging NOT with appv but in another way?
The error does NOT occur during RUN or Customize or Streaming in the APPV sequencer. But when all is imported in the seq. server and I start it up from a client.
-
Wednesday, November 09, 2011 2:10 PMModerator
Correct, App-V can't be used to package drivers in any way. You'll need to deliver them with some other means such as an MSI. the Sequencer will give you an idea of what makes up those drivers.
The issue probably doesn't occur during sequencing because the drivers get installed on the sequencing machine.
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
Wednesday, November 09, 2011 3:27 PM
Thanks Aaron, first 10 days holiday. Then back to App-v again .
Something to think about !.. ha ha .
gr.Pvds.
-
Wednesday, November 23, 2011 10:15 AM
I contacted a consultant from the application supplier EXACT. They told me that it is not possible to virtualize Exact Globe 4.0 with appv 4.5
They are testing with appv version 4.6 SP1 . I'll ask them to give me a mail when they are done!.
gr. PVDS
- Proposed As Answer by znackMVP Wednesday, November 23, 2011 10:17 AM
- Unproposed As Answer by Aaron.ParkerMVP, Moderator Sunday, January 08, 2012 10:21 PM
-
Tuesday, November 29, 2011 3:03 PM
As always, Exact support are talking out their backsides, I have a copy of 4.0 running happily in appv 4.5. Try the below.
The excel.xlb file below is for excel integration, let me know if you need it.
before sequencing:
- install office before sequencing as a prerequisite
- install .net framework 3.5 as a prerequisite
- launch excel, accept any popups, close excel and open it again, ensure you get no popups.
- close excel
start the sequence:
- install exact to sftdrive:\packagename
- DONT LAUNCH EXCEL OR EXACT!
- browse to%userprofile%\application data\Microsoft\Excel
- copy excel.xlb here
- stop both exact services
- disable both exact services
- stop and disable the messaging service if needed.
- change the indexing service to manual if needed.
- Stop the sequence.
Post tasks:
Ensure to uncheck "enforce security descriptors".for excel integration:
once saved, edit the osd to include the following value:
<REGKEY HIVE="HKCU" KEY="Software\Microsoft\Office\12.0\Excel\Options">
<REGVALUE REGTYPE="REG_SZ" NAME="OPEN">"C:\Program Files\microsoft office\office12\library\eg2000.xla"</REGVALUE>
</REGKEY>
- Proposed As Answer by Aaron.ParkerMVP, Moderator Tuesday, November 29, 2011 3:14 PM
- Marked As Answer by Aaron.ParkerMVP, Moderator Sunday, January 08, 2012 10:22 PM
-
Wednesday, January 25, 2012 8:19 AM
Dear Andrew,
Nice example how to do it. Partly this was the way how I did it. I'm now in a test period and found out some problems. Maybe you can help me with it.
· Every time when there is an update, it will be shown to all users. Is there a way to turn this off? How did you handle updates.
· The plug-in part (XLS) is not working for me. I did not add this to my package. Can you please explain the excel.xlb part and how do I get/make this file...
· What does the registry part do which I need to add to the OSD file? There is no such file eg2000.xla stored on this location on a machine. Or will this be installed during installation and is it inside the bubble.
Is there a way how I can contact you per mail?
Regards,
Rob van den Broek -
Tuesday, February 14, 2012 7:56 AM
Is there any more information about the excel.xlb and the update question?
Where can I find this Excel.xlb file for Excel 2010?
-
Tuesday, February 14, 2012 7:56 AM
Is there any more information about the excel.xlb and the update question?
Where can I find this Excel.xlb file for Excel 2010?
-
Thursday, February 16, 2012 11:43 AM
Hi,
It's been a while since I sequenced this program.
The XLA file should be created on the sequencer as part of the install of exact,assuming you install office prior to sequencing.
The flavor of office I used was 2007 hence ..\office12\.. if you are using office 2010, this folder would be office14.
The registry key tells office to launch this program on startup, so when Exact exports to excel, excel launches and see's this addin.
The locally installed copy of excel can't by default see the addin, if you wish to use excel with the addin you'll need to create a shortcut to excel as a virtual application and also include this registry key.
The xlb file is a bar file generated after the first launch of excel with the Exact plugin, Install exact natively and launch excel, you should find the xlb file at that point. Take a copy of this. Once you have a clean one, copy it in as part of the sequence.
The xlb file tends to get corrupted easily, it was always safer in our case to copy in a clean copy.
- Edited by Andrew J Morgan Thursday, February 16, 2012 11:44 AM
-
Thursday, February 16, 2012 1:10 PM
Thanks! this point is clear now, but I keep getting the same error as TS has.
I think it has something to do with the services, I can't disable them during sequence. Have to still to try it with SC. The installation is allmost 1.5 GB so quick testing is not possible...
-
Thursday, February 16, 2012 1:10 PM
Thanks! this point is clear now, but I keep getting the same error as TS has.
I think it has something to do with the services, I can't disable them during sequence. Have to still to try it with SC. The installation is allmost 1.5 GB so quick testing is not possible...
-
Wednesday, April 25, 2012 10:48 AM
I have exactly the same problem. Tried everything always the automation error.
I can't disable the services as well during sequence.
-
Tuesday, June 05, 2012 2:04 PM
Ok I found out with procmon why it gives the automation error. If you install Exact on the Q-drive (e.g. Q:\EXACT.R01) Exact will register all DLL-files after the installation, however Q:\ is a symbolic link to C:\Programdata\Microsoft\Application Virtualization Sequencer\Package Root\Exact.R01\, so Exact is looking for the files there.
I don't know if there's any difference when you create a Q-drive from an additional disk instead of letting the App-V sequencer create it. That's what I'm gonna try next. The workaround seems to not install it on the Q-drive but use the default path, C:\Program Files (x86). -
Tuesday, June 05, 2012 2:38 PM
Here's the solution:
http://kirxblog.wordpress.com/2011/05/13/defective-component-registration-with-4-6-sp1-sequencer/
- Edited by Aaron.ParkerMVP, Moderator Tuesday, June 05, 2012 7:31 PM Fixed URL

