SharePoint PrerequesiteInstaller fails if .vbs file extension is not registered correctly
Posted by Matthias Einig in SharePoint, SQL on May 15, 2012
When installing SharePoint 2010 and the .vbs file extension is registered to something else than VBSfile in the Windows registry (in my case to Notepad++ on my new DEV machine) , then the PrerequisiteInstaller will fail with the error
Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
When running the installation with AutoSPInstaller you will only get the cryptic message:
... ------------------------------------------------------------- -------------------------------------------------------------- - Installing Prerequisite Software: - Running Prerequisite Installer... -------------------------------------------------------------- Script aborted! Exception : System.Management.Automation.ParameterBindingValidation Exception: Cannot bind argument to parameter 'Message' because it is null.
In the logfile of PrerequisiteInstaller you can find the command which is causing the issue
"C:\Windows\system32\cscript.exe" "C:\Windows\system32\iisext.vbs" /enext "ASP.NET v2.0.50727"
Which obviously activates ASP.NET v.2.0 in IIS
Running that command manually reveals the issue
C:\Install\SharePoint>"C:\Windows\system32\cscript.exe" "C:\Windows\system32\iisext.vbs" /enext "ASP.NET v2.0.50727" Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Input Error: There is no script engine for file extension ".vbs".
The fix isto go into Registry editor, navigate to HKEY_CLASSES_ROOT\.vbs and change the “(Default)” entry from Notepad++ file back to the standard vbsfile.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.vbs]
; @="Notepad++ file "
; change the default value from Notepad++ file back to vbsfile
@="vbsfile"
"Content Type"="application/x-vbscript"
[HKEY_CLASSES_ROOT\.vbs\PersistentHandler]
@="{5e941d80-bf96-11cd-b579-08002b30bfeb}"
[HKEY_CLASSES_ROOT\.vbs\ScriptEngine]
@="VBScript"
see also
http://jamesmcdonald.id.au/it-tips/input-error-there-is-no-script-engine-for-file-extension-vbs
Error with TFS2010 and remote Analysis Services on SQL2012
Posted by Matthias Einig in Setup, TFS on May 10, 2012
If you are trying to get Team Foundation Server 2010 to run with MS SQL Server 2012 Analysis and Reporting services, forget it 
After getting this error in Team Foundation Administration Console
“Could not load file or assembly ‘Microsoft.AnalysisServices.AnalysisServices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′ or one of its dependencies”
I first thought it had to do with the “Client Tools Connectivity” of SQL Server which are required on the TFS application Tier.
After some digging I finally realized, that I missed the obvious.
The SQL2010 assembly has a different version!!!
‘Microsoft.AnalysisServices.AnalysisServices, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91′
So it will never work with SQL2012 connectivity tools at least until now with TFS SP1.
Update:
If you install SQL Server 2008R2 Client Tools Connectivity on TFS Application Tier and SQL Server 2012 Client Tools Connectivity (Backwards Compatibility) on the SQL 2012 server it seems to work!
Unfortunately I still have to solve the annoying TF255186 Error with Reporting Services on SQL2012…
Update 2:
Solved!!! Finally solved the last issue by naming the Reporting Services ReportManager URL and WebServices URL by following schema:
http://<ReportServer>/Reports_<InstanceName>
http://<ReportServer>/ReportServer_<InstanceName>
This of course won’t be necessary when your reporting server runs on the default instance of SQL.
Thank you MS for not pointing out that this seems to be a requirement…
SharePoint Software Factory 3.2 released!
Posted by Matthias Einig in SharePoint, SPALM, Visual Studio on February 13, 2012
We have released a new version of SPSF on Codeplex
Release Notes
- Menu “List And Doc”: Linq to SharePoint (imports the schema of several lists to LINQ classes)
- Menu “BCS”: Simple BCS Model
- Menu “BCS”: Import BCS Model from Database
- Menu “BCS”: Model BCS Model with classes
- Menu “BCS”: Quick Deploy BCS Model (undeploys/deploys BCS model via powershell)
- Menu “Security”: Minimal CAS, Medium CAS, recipes for single CAS Policy Items etc.
- Menu “ASP.NET”: WCF Webservice
- code snippets added, partly from http://spcodesnippets.codeplex.com Thx to Ayman El-Hattab (http://aymanelhattab.com)
- Added custom FxCopDictionary to allow project specific exclusions for abbreviations, keyword, acronyns etc. Dictionary will be automatically used in Realase build configuration.
Improvements
- ParametersDefault.msbuild sets RestartIIS to false by default
- ParametersDefault.msbuild updated sample structure to allow easy setup of multiple deployment environments
- In selection form of fields or content types the group is displayed (e.g. for field “Title” there are 6 results and no difference)
- SharePointVersions.xml with current version numbers
- Added BCS extensions (DBML, BDCM) to function “IsExcludedExtension” to avoid that model layout is saved to the WSP file
- Change default.aspx in site defition Team Site and Blank Site to version 2010
- In feature selection dialog a existing feature of allowed scope is selected by default
- StartDeploy.bat: Made verbosity for ULSLogger configurable (previously it was always diagnostic)
Bugfixes
- Deployment.msbuild added ” by default for stsadm path
- Deployment.targets corrected stsadm and powershell examples
- Codeplex ID 6253: Typo for Ribbon Group Document
- Codeplex ID 6170: Webservice Error creating WSDL and DISCO when Windows SDK is not installed
- Codeplex ID 6190: Code Snippets are not correct
- Corrected FxCopConsoleOutput.xls to display Critical and Errors of FXCop in Release build as errors instead of warnings in the Error List of VS
- Create inital .csproj.user with SiteDebuggingUrl for SharePoint WSP projects
- ListInstance recipe refrenced language resources in global resource file, instead of feature resource file
- Search for gacutil fixed
- SharePointTargets.targets for HIVE: added parameter for text templating generation (” -P <path to referenced assemblies>”) to allow loading of assemblies needed for SafeControl entry
- SharePointTargets.targets: Changed $(IsDesktopBuild) to $(BuildingInsideVisualStudio) to allow team build in TFS 2010
- MSBuild ULSLogger: Changed date format to InvariantCulture to overcome issues with ULSViewer
- MSBuild ULSLogger: Applying log level to all messages to be able to reduce file size of log files for larger deployments
Exception when installing SQL Server 2008 R2
Posted by Matthias Einig in SQL on October 8, 2011
When you try to install SQL Server 2008 R2 and get the following exception
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly ‘System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′ or one of its dependencies. The system cannot find the file specified. (C:\Documents and Settings\<UserName>\Local Settings\Application Data\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5)
delete the folder
C:\users\<UserName>\Local Settings\Application Data\Microsoft_Corporation\