issue in package creation
I am creating a package of Power Path application for Windows 2008 R2 server. When i am installing the exe file and application is working fine. but after creating the package and installing that application is not working properly.
Error says that "RPC server is not available. Please verify that EMC power path service is started."
Manually check the service it started. Also the size of MSI is too big (94 MB) but he exe is only 50 MB in size.
Please suggest me where i am wrong.
Error says that "RPC server is not available. Please verify that EMC power path service is started."
Manually check the service it started. Also the size of MSI is too big (94 MB) but he exe is only 50 MB in size.
Please suggest me where i am wrong.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Does your package start the service after installing it?
"Too big" LOL. There's nothing you can do about the final size of an MSI if it includes all the files required by the application. Maybe you could trim it down by removing, say, language files you don't need but, really, why bother? 94Mb is nothing these days.
"Too big" LOL. There's nothing you can do about the final size of an MSI if it includes all the files required by the application. Maybe you could trim it down by removing, say, language files you don't need but, really, why bother? 94Mb is nothing these days.
Posted by:
bini2082
13 years ago
Yes. I have include the service in package and the service start after installing.
Posted by:
naveen.packager
13 years ago
Is it giving the error in admin mode itself?
you can use procmon to check what exactly it is lookig for.
you can use procmon to check what exactly it is lookig for.
Posted by:
dunnpy
13 years ago
It seems that someone else has had the same error when upgrading EMC Powerpath - here
Their solution was to uninstall and reinstall the application, which would seem to indicate that some setting/configuration was missing/incorrect.
I would suggest installing your package and then running a 'Gap Capture'.
Use your favourite light-weight snapshot tool (inControl, InstallRite et al) and report on the installation of the vendor's installer over the top of your MSI.
This will show you if anything has been missed in your package, and what you need to pull into your MSI to resolve your issue.
Hope this helps,
Dunnpy
Their solution was to uninstall and reinstall the application, which would seem to indicate that some setting/configuration was missing/incorrect.
I would suggest installing your package and then running a 'Gap Capture'.
Use your favourite light-weight snapshot tool (inControl, InstallRite et al) and report on the installation of the vendor's installer over the top of your MSI.
This will show you if anything has been missed in your package, and what you need to pull into your MSI to resolve your issue.
Hope this helps,
Dunnpy
Posted by:
kanthsri87
13 years ago
Jus check whether u added the service through service control table or thro registries since u captured the appln most probably it wil b added in HKLM \sytem\current control set\services
In order to start the service u need a reboot !!Jus check it once!!
If u added the service via Service control table its not required.
In order to start the service u need a reboot !!Jus check it once!!
If u added the service via Service control table its not required.
Posted by:
anonymous_9363
13 years ago
In order to start the service u need a rebootOnly kernel-level services require a reboot.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.