I'm having a problem with Wix Service as the service cannot be started during install progress. It throws the error:
Error 1053: The service did not respond to the start or control request in a timely fashion
I've tried with both [WIX_ACCOUNT_LOCALSYSTEM] and [WIX_ACCOUNT_LOCALSERVICE] but no one of them work.
But there is weird here as I have an installer which using ClickOne, it includes the same service component as the one I have been using in Wix. The ClickOne installs service just fine (using InstallUtil.exe), so it proves the account has right to start a service.
Then, I uninstall the software (installed by ClickOne), and running the Wix installer again, the service starts well now. I don't know the reason why?
I'd like to put some flows for more clearly:
1- On a fresh machine
2- Running Wix software installer --> the service cannot be started and throwing error message --> Cancel install
3- Running ClickOne software installer --> service starts well --> Uninstalling software
4- Running Wix software installer --> service starts well
Also note that, I've tried 2 times on 2 fresh machines but it's the same. Anyone can shed some light on this weird behavior? Or anything I should verify against?
Thanks in advance,
Thank you #Stephen Connolly, #Alexey Ivanov, #Cosmin Pirvu for your comments.
I'd like to add your comments above as the answer.
Using CheckAsm, a great tool to verify the assembly dependencies
Looking at the log information in Event Viewer for anything could stop the service starting (i.e. timeout, services dependency ...)
Verifying all stuffs would be needed for service operations. They should be available once installation completed (i.e. configuration, registry, working folder ...)
If the installer is installing files to the GAC using the Windows Installer tables, the dependencies won't be available when the installer runs the StartServices action
Related
After upgrade to sdk 2.5.216 and runtime 5.5.216 Test-ServiceFabricApplicationPackage command works only for complete package. In case of partial app upgrade (some Pkg are removed) it results in "Windows PowerShell has stopped working". I have tested on several computers and several apps. to reproduce:
create test app with 2 services and deploy.
change app version and particular service version.
create package and remove Pkg folder from it for the service without modifications.
connect to Service Fabric and test like Test-ServiceFabricApplicationPackage -ApplicationPackagePath "..path" -ImageStoreConnectionString "fabric:ImageStore"
Maybe somebody was able to overcome this issue? or at least has similar behavior so I'm not alone in Universe.
Thanks!
Alex
Take a look at https://github.com/Azure/service-fabric-issues/issues/259
This is a bug in our code. It happens when a compressed package was uploaded and provisioned in the cluster. Testing a new version of the application fails because settings file was not found in the provisioned version.
We fixed the issue and it will become available in one of our next releases.
Meanwhile, you can skip compression or test the version 2 application package without passing in the image store connection string.
Apologies for the inconvenience!
I have tried to upgrade to the ne version of the Service Fabric preview code - 1.4.87-preview - and everything seems to have gone ok, but when I try to deploy a service I get an exception on run telling me that it cannot find FabricRuntime.dll. This goes both for my upgraded project, for newly created test projects and for all samples.
I can see that the DLL is present on the machine and that a system PATH has been set to the directory containing it.
There seems to be nothing wrong with my applications per se, as they deploy fine to a Party Cluster.
Anybody have any idea what is going on. Everything worked fine when I ran the old Service Fabric install. I have tried uninstalling service fabric and installing again, but it didn't help.
The answer is now posted on MSDN forums at https://social.msdn.microsoft.com/Forums/azure/en-US/6c8cc261-6c84-4097-be03-e8073cbc9397/unable-to-load-dll-fabricruntimedll?forum=AzureServiceFabric&prof=required
Copy of answer from MSDN Forum:
This is happening because FabricRuntime.dll is looking for zip.dll that ships with Service Fabric runtime. However since JRE is ahead in the PATH list and it also ships with a zip.dll, FabricRuntime tries to load zip.dll from the JRE folder and fails. We have fixed this issue by renaming our DLLs. The fix will be available in the next update of the SDK. In the meanwhile, you can fix this by adding "C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code" as the first entry in the system path and then restarting the machine.
This is the SDK issue, I've opened a GitHub issue at here
We upgraded firewall firmware on servers, and the firmware update contains shellshock protection.
Suddenly whenever we do deploy with Capistrano the firewall block our office so we get "Blocked because of IPS attack" from firewall.
I bundle update Capistrano and all dependencies to latest version and same result. Anyone had and know fix for this issue ?
my versions
capistrano (3.2.1 8290d3f)
capistrano-bundler (1.1.3)
capistrano-rails (1.1.2)
capistrano-rbenv (2.0.2)
The problem was me being too stupid. Few weeks ago I installed extension to my browser for specifying custom headers. I created some custom malicious headers and was trying to crack my page to see what will happen. Of course I forget to turn it of.
each time I was doing deployment I checked it with the web-browser (with faulty extension) therefore locking my access and blaming it on deployment.
more info here https://github.com/capistrano/capistrano/issues/1176#issuecomment-62020915
I create One Windows services to scheduling SQL backup,
Its runs perfectly when i install it by visual studio command prompt, installutil services.exe,
Now i need to make it setup so, i can give this services to my client also,
I found http://support.microsoft.com/kb/816169 this link very userful
i create setup file, and it also install services,
but when i start services by right click on service,
it start perfectly in my PC but in other Pc its shows error
kindly help me to create setup file for services
I think you see that message when the service is started by the system but stops quickly without completing the protocol message/event exchange. Your service is starting and then just finishing, so you need to figure out what it's doing, even if it's just "On Exception go to end of program".
I'm trying to deploy my HelloWorld application in Windows Azure which was developed in Java using eclipse. The application working fine when I tested under tomcat and Azure sdk. I created hosted service in Window Azure Management Portal and deploy my application. It almost 3 hours and it still deploying.
I went to What Happens When You Deploy on Windows Azure? and checked but still unclear.Can anyone advice why it took so long to deploy and any suggestion how to make the deployment process more faster.
Please refer the image below.
I changed the startup.cmd, instead of copy my tomcat to azure i changed the startup.cmd to download the tomcat online. now its working fine.
Does you start-up script finish after tomcat start?
The instances will be marked as ready only after the start-up script finished, so if you start tomcat blocking the start-up script it won't reach this state unless tomcat crashes...
You should use "start" (http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/start.mspx?mfr=true) command to start tomcat in a separated process allowing the start-up script to finish.
(In my memories the provided example in the eclipse plugin had the issue)