Trying to install custom template pack on W2K8

[amiles248]

When I attempt to install a custom template pack I receive the following error:

"There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact you support personnel or package vendor."

I read on-line that there are known issues with installing MSI files on w2k8 so i tried the following:

*Turned off User Access Controls and ran the msi again, Result: Same error as above

*Ran msiexec.exe /a saber.msi in administrator console Result: No error, script ran and disappeared but did not install

*Ran msiexec.exe /l*v log.txt /i "saber.msi" in administrator console Result: This gave me the same error as above but did yield an error log with the following errors:

Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action CheckPackValidity script error -2147024774, : Line 13, Column 1,

MSI (s) (84:B4) [23:16:22:491]: Product: Parallels Sitebuilder for Windows Saber1-108 Template Pack -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action CheckPackValidity script error -2147024774, : Line 13, Column 1,

Property(S): DBCONNECT_ERROR = Could not connect to Sitebuilder database. Installation is not complete.

Property(S): DBUPDATE_ERROR = An error occured while updating Sitebuilder database. Installation is not complete.

Property(S): SecureCustomProperties = ASPUSER;DBCONNECT_ERROR;DBUPDATE_ERROR;EARLY_VERSION_FOUND;INSTALLDIR_REP;INSTALLDIR_SB;INSTALLED_PRODUCTCODE;INSTALLED_VERSION;INSTALLMODE;INSTALLMODE2;LATER_VERSION_FOUND;OLDESTFOUND;PACK;SUPPORTED_TFV;TEMPACKMSG_NEWERFOUND_ERROR;TEMPLATE_ALREADY_INSTALLED;TEMPLATE_FORMAT_VERSION;TEMPLATES_LIST;WRONG_TEMPLATE_FORMAT_VERSION;WSBFOUND

MSI (c) (E4:AC) [23:16:22:870]: Note: 1: 1708

MSI (c) (E4:AC) [23:16:22:871]: Note: 1: 2205 2: 3: Error

MSI (c) (E4:AC) [23:16:22:871]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708

MSI (c) (E4:AC) [23:16:22:871]: Note: 1: 2205 2: 3: Error

MSI (c) (E4:AC) [23:16:22:871]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

 

[abobykin]

Please check that template code name does not contain spaces " ".

 

[amiles248]

All of the template folders are named like this: "Saber01" "Saber02" "Saber108"

The sbtp file was called "Saber.sbtp"

Inside the file:
name="Saber1-108"
type="Windows"


The Template Packager is running Version 4.2.31

 

[abobykin]

Line 13:

ret = WshShell.Run (Chr(34) + GetProp("INSTALLDIR_SB")+ "Utils\UpdateTemplatesConsole.exe" + Chr(34) + " -c " + " " + GetProp("TEMPLATES_LIST"),2,True)

So it tries to run UpdateTemplateConsole -c "Saber01,Saber02,Saber108"

Please check why this launch may fail.

 

[amiles248]

I don't see "wshshell" or "UpdateTemplateConsole" anywhere in the log file.

Just to clarify there are 108 templates in this package.

 

[abobykin]

Folder names for all 108 templates are added as "TEMPLATES_LIST" parameter. So if at least one template code contains space " " - this schema will not work. Please check this 108 names.

 

[amiles248]

No spaces that I can see:

<?xml version="1.0"?>
<templatePack name="Saber1-108" type="Windows">
<directory path="Saber01" />
<directory path="Saber02" />
<directory path="Saber03" />
<directory path="Saber04" />
<directory path="Saber05" />
<directory path="Saber06" />
<directory path="Saber07" />
<directory path="Saber08" />
<directory path="Saber09" />
<directory path="Saber10" />
<directory path="Saber11" />
<directory path="Saber12" />
<directory path="Saber13" />
<directory path="Saber14" />
<directory path="Saber15" />
<directory path="Saber16" />
<directory path="Saber17" />
<directory path="Saber18" />
<directory path="Saber19" />
<directory path="Saber20" />
<directory path="Saber21" />
<directory path="Saber22" />
<directory path="Saber23" />
<directory path="Saber24" />
<directory path="Saber25" />
<directory path="Saber26" />
<directory path="Saber27" />
<directory path="Saber28" />
<directory path="Saber29" />
<directory path="Saber30" />
<directory path="Saber31" />
<directory path="Saber32" />
<directory path="Saber33" />
<directory path="Saber34" />
<directory path="Saber35" />
<directory path="Saber36" />
<directory path="Saber37" />
<directory path="Saber38" />
<directory path="Saber39" />
<directory path="Saber40" />
<directory path="Saber41" />
<directory path="Saber42" />
<directory path="Saber43" />
<directory path="Saber44" />
<directory path="Saber45" />
<directory path="Saber46" />
<directory path="Saber47" />
<directory path="Saber48" />
<directory path="Saber49" />
<directory path="Saber50" />
<directory path="Saber51" />
<directory path="Saber52" />
<directory path="Saber53" />
<directory path="Saber54" />
<directory path="Saber55" />
<directory path="Saber56" />
<directory path="Saber57" />
<directory path="Saber58" />
<directory path="Saber59" />
<directory path="Saber60" />
<directory path="Saber61" />
<directory path="Saber62" />
<directory path="Saber63" />
<directory path="Saber64" />
<directory path="Saber65" />
<directory path="Saber66" />
<directory path="Saber67" />
<directory path="Saber68" />
<directory path="Saber69" />
<directory path="Saber70" />
<directory path="Saber71" />
<directory path="Saber72" />
<directory path="Saber73" />
<directory path="Saber74" />
<directory path="Saber75" />
<directory path="Saber76" />
<directory path="Saber77" />
<directory path="Saber78" />
<directory path="Saber79" />
<directory path="Saber80" />
<directory path="Saber81" />
<directory path="Saber82" />
<directory path="Saber83" />
<directory path="Saber84" />
<directory path="Saber85" />
<directory path="Saber86" />
<directory path="Saber87" />
<directory path="Saber88" />
<directory path="Saber89" />
<directory path="Saber90" />
<directory path="Saber91" />
<directory path="Saber92" />
<directory path="Saber93" />
<directory path="Saber94" />
<directory path="Saber95" />
<directory path="Saber96" />
<directory path="Saber97" />
<directory path="Saber98" />
<directory path="Saber99" />
<directory path="Saber100" />
<directory path="Saber101" />
<directory path="Saber102" />
<directory path="Saber103" />
<directory path="Saber104" />
<directory path="Saber105" />
<directory path="Saber106" />
<directory path="Saber107" />
<directory path="Saber108" />
</templatePack>

 

[abobykin]

I will check with QA. Maybe this win2k8 specific issue. Can you recheck it on win2k3?

 

[amiles248]

Unfortunately not. I only have 4.1 on W2k3 and it's a production server. I did however package these using the 4.1 sdk and it installed just fine.

On a side note, do you any websites that sell template packs for sitebuilder?

 

[abobykin]

No. I think you will be first.

 

[amiles248]

Any updates on this issue?

 

[abobykin]

Can you reproduce the issue with only one or two templates in template pack?
If yes, can you give me the source?

 

[amiles248]

Ok, mystery solved. The database needed windows passthough authentication in order for MSI to install the templates to the database. Once I made this change the templates installed. Thanks for your help abobykin