a customer has a problem deploying a webpart I developed for them on a farm. The webpart is packaged as a .WSP solution with WSPBuilder and it seems to work fine when deployed to a single server.
When customer tries to deploy it to the farm, the deployment batch file goes through OK, but the feature doesn't show up in Sharepoint and there seem to be no errors.
The install batch file contains the following:
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o retractsolution -name "MCTPlanogramSharepointWebPartDeploy-prod.wsp" -immediate -allcontenturls
rem Izvedi ukaz
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execadmsvcjobs
rem Nato odstranimo WSP solution, ce ze obstaja
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o deletesolution -name "MCTPlanogramSharepointWebPartDeploy-prod.wsp"
rem Izvedi ukaz
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execadmsvcjobs
rem Dodaj WSP solution
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o addsolution -filename "MCTPlanogramSharepointWebPartDeploy-prod.wsp"
rem Izvedi ukaz
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execadmsvcjobs
rem In naredi deployment na vse contentUrl. Ce zelimo naredimo deployment na poseben URL, umaknemo parameter -allcontenturls in dodamo -url http://imekamhocemodat
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o deploysolution -name "MCTPlanogramSharepointWebPartDeploy-prod.wsp" -immediate -allcontenturls -allowGacDeployment -allowCasPolicies -force
rem Izvedi ukaz
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o execadmsvcjobs
This is what the customer sent:
Name: mctplanogramsharepointwebpartdeploy-prod.wsp
Type: Core Solution
Contains Web Application Resource: Yes
Contains Global Assembly: Yes
Contains Code Access Security Policy: No
Deployment Server Type: Front-end Web server
Deployment Status: Not Deployed
Deployed To: None
Last Operation Result: The solution was successfully deployed.
Last Operation Details: MOSS-I : http://moss.mercator.si/ : The solution was successfully deployed.
MOSS-I : https://portal.mercator.si/ : The solution was successfully deployed.
MOSS-I : https://ssp-moss.mercator.si/ : The solution was successfully deployed.
MOSS-A : http://moss.mercator.si/ : The solution was successfully deployed.
MOSS-A : https://portal.mercator.si/ : The solution was successfully deployed.
MOSS-A : https://ssp-moss.mercator.si/ : The solution was successfully deployed.
MOSS-A : http://moss.mercator.si/ : The solution was successfully deployed.
MOSS-A : https://portal.mercator.si/ : The solution was successfully deployed.
MOSS-A : https://ssp-moss.mercator.si/ : The solution was successfully deployed.
MOSS-B : http://moss.mercator.si/ : The solution was successfully deployed.
MOSS-B : https://portal.mercator.si/ : The solution was successfully deployed.
MOSS-B : https://ssp-moss.mercator.si/ : The solution was successfully deployed.
The features in the wsp packages have their Scope set to Site - should they be set to FARM? Are there any other differences when deploying to the farm that I should be aware of? Do they need to run the stsadm commands on every frontend server?
If someone can point me to some documenation for this specific scenario I'd be grateful.