I think you didn't register some COM object used by service and that's why it can not start.
Did this service ran OK when you captures application - before post-scan?
It ran ok, but i seems i didnt activate it in the ini file, i´ll try it know and see if it works.
It seems that i must use thinreg with /a to register the service. If I only run the .exe without doing thinreg, I get the error msg. But when i look at the processes the serive is started and listed there.
Read manual http://www.vmware.com/pdf/thinapp461_manual.pdf at page 46
I did that and it work, but there isent another way to run the services?
Services should autostart when you launch a ThinApped application. If it doesn't it might simply be a timing issue, the service hasn't started before the application is launched. There is a package.ini parameter called AutoStartServices. By default this is =1 which means it will start services. Just make sure you do not have AutoStartServices=0 in yours. Cannot see a reason why that would be but anyway..
Hi
I cant find any parameter that is AutoStartServices in my package.ini file.
Can you, please, attach Package.ini file to this thread?
And also, please, write name of service.
Dude, please, edit your post with all those info from file and JUST ATTACH FILE INTO POST ![]()
It looks that after compilation your entry point TestCompleteService7.exe is created. After compilation just run:
thinreg.exe /a TestCompleteService7.exe
and this should register service into your system.
Sorry for that.
I did do thinreg.exe /a and it work. But my question is: must i do thinreg.exe /a? I want tje service to start without to do thinreg /a, or is that impossible?
Thank you
I think it's possible, but you need to create service manually with entrypoint as binpath (http://support.microsoft.com/kb/251192). Thinreg.exe does it for you automatically.
Boot time services are possible if that is what you are looking for.
When capturing your application with ThinApp, services will also be capture. Before building the package, go into the PACKAGE.INI file and look for the [{Entry Point}] specific values (where {Entry Point} is the name of your service executables).
[Entry Point]
;Services={service_name}
Disabled=1
To make this virtual service appear as a Windows boot time service, unremark the Services= line and change Disable=1 to Disabled=0 (or just delete that line) and then build your package.
As an example, I'm posting an Entry Point for the .NET FrameWork service for an application which needs .NET FrameWork started and running. While this isn't needed for the ThinApp package to work (as the ThinApp package would just autostart the service), the end users complained of the startup time - therefore, registering the .NET FrameWork service within the ThinApp package as a service in the native system gets the ThinApp package launched on startup/login for the user.
Here you will note I removed the "Disabled=1" line and the Services line is bolded.
[mscorsvw.exe]
Source=%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe
Shortcut=PaintDotNet.dat
Services=clr_optimization_v2.0.50727_32
Icon=%SYSTEMROOT%\SYSTEM32\Shell32.dll,14
-Dean F.
http://pubs.vmware.com/thinapp4/help
