The following are the most commonly requested installation related solutions.
Can’t extend resources on new installation
When attempting to extend a SQL Resource in a new installation, the Extend Wizard may yield the following information:
“An extend script with a supported extension (.ksh,.pl or .ps1) does not exist or is not executable for database/sqlapp”
It was determined that the \sqlapp folder was missing, which is located at C:\LK\Subsys\database\resources.
Also the “LifeKeeper Microsoft SQL Server Recovery Kit” was not listed in Control Panel\Programs\Programs and Features.
- Deploy/use the latest software available
- Verified the folder was present C:\LK\Subsys\database\resources\sqlapp
- Delete the hierarchies i.e. SQL.Default, Volumes
- Recreated the aforementioned and successfully extended the SQL resource
LifeKeeper GUI cannot launch after upgrade
- Upgraded to the latest version of the software
- LifeKeeper GUI can no longer launch
It was determined that the LifeKeeper GUI was opened during the upgrade. Notifications are posted via the Install Wizard identifying that the GUI is open and you should close it accordingly, but by selecting “No”, to bypass closing the GUI will allow you to continue with the installation.
Performing the aforementioned will cause the upgrade to NOT update certain files, i.e. lkGUIapp.P1.
Execute a repair on the the LifeKeeper installation . . .
- Close the LifeKeeper/DataKeeper GUIs
- Run a repair on LifeKeeper as this can be located at:
- Control Panel\Programs\Programs and Features
- Then right select “LifeKeeper for Windows V8 update x Maintenance x”
- There will be a “Uninstall/Change” option present, preceded by “Repair”
A reboot will be required upon completion.
Now the LifeKeeper GUI can launch properly.
Post your comment on this topic.