I am installing the Reference Implementation for the first time on an SDL Tridion 2013 SP1 CM/CD server.
I have encountered a few problems and thought I would document the ones I fixed here and see if I could get some help on the ones I can't.
The two issues I solved:
- System.Web.Infrastructure missing when first loading the application (same error as here: https://stackoverflow.com/questions/12669206/error-microsoft-web-infrastructure-version-1-0-0-0-culture-neutral-publickeyt) - installing MVC4 on the server fixed this.
Could not load file or assembly 'System.Web.Helpers, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified."when trying to publish "_System/Publish Settings" page. I think this was also caused by missing DLLs in the GAC. Restarting the TCM and Publisher solved this after installing MVC4 (I did restart the server after installing .NET 4.5.1)
The two I can't resolve:
When accessing the web application I see:
[ArgumentNullException: Value cannot be null.Parameter name: paths] System.IO.Path.Combine(String paths) +6626904 Sdl.Web.Common.Mapping.SemanticMapping.Load(String applicationRoot) +379 Sdl.Web.Common.Configuration.SiteConfiguration.Refresh() +304 Sdl.Web.Site.MvcApplication.Application_Start() +343`
I thought this was to do with the settings not being published but I have restarted the app after getting them published and not got anywhere.
I am unable to publish the "Publish HTML Design" page with the following error:
'C:\Program' is not recognized as an internal or external command, operable program or batch file.
Has anyone else experienced these issues and can help?
After getting past 2 - due to installing 32 bit Node.js. I have the below error:
Error: ENOENT, stat 'C:\Windows\system32\config\systemprofile\AppData\Roaming\npm'
I have tried setting all the permissions I can think of on this folder including SYSTEM->Full Control, Everyone->Full Control. My TCMPublisher service is running as Local System.
Update My final error was resolved by uninstalling Node.js 32 bit and installing Node.js 64 bit