Troubleshooting

In this article

In this page

Automating on this scale invariable will not always go smoothly. This page will be updated over time with common issues.

Known issues

Issue	Symptom	Work Around	Status
Path Spacing	If you run the scripts from a path with a space in it, eg; "C:\Deploy 1.0\..." external scripts error with Script is not recognized as the name of a cmdlet, function, script file, or operable program.	Do not include spaces in the path to the deployment scripts.	Not yet scheduled
Managed Accounts	If the identity of the application pool account specified in the PortalAppPoolAcct element is not one of SharePoint's known managed accounts you receive and error stating the Application Pool does not exist.	Add the managed account in Central Admin under the Security Section.	Not planned
Script Parameters with spaces	If a script uses a parameter that includes a space you may only get the first characters before the space passed to the script when it is executed.	Add quotes " around the parameter. eg; <Parameter Name="SiteTitle">"This title needs quotes"</Parameter>	Not yet scheduled

Error	Possible Cause
Application Pool Is Not Found	You have to create a Managed Service account in Central Admin for your Application. The value of the PortalAppPoolAcct element within the DefaultParameters maybe spelled incorrectly. The value of the PortalAppPoolAcct element within the WebApplication element maybe spelled incorrectly.