Failed to Install Application Content Files Error
I'm migrating from WSS2.0 to WSS3.0 - standalone server, in-place migration. Very simple sharepoint with no customized functionality. I've followed the steps in TechNet to the letter, and the installation proceeds without a hitch. Configuration throws the following error after step 8:Failed to install application content filesAn exception of type System.ArgumentException was thrown. Additional exception information: Version string portion was too short or too long.The relevant portion of the install logs is here (from the command line):[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: ReflexiveUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)[SPManager] [DEBUG] [2/25/2007 10:29:52 PM]: Disposing Microsoft.SharePoint.Administration.SPIisWebSite.[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Resetting the status of PersistedUpgradableObject: SPWebApplication Name=Default Web Site Parent=SPWebService to Online.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: ReflexiveUpgrade [SPWebApplication Name=Default Web Site Parent=SPWebService] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Resetting the status of PersistedUpgradableObject: SPWebService Parent=SPFarm Name=STS_Config to Online.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: ReflexiveUpgrade [SPWebService Parent=SPFarm Name=STS_Config] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Resetting the status of PersistedUpgradableObject: SPWebServiceInstance Parent=SPServer Name=D4P6YS61 to Online.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: ReflexiveUpgrade [SPWebServiceInstance Parent=SPServer Name=D4P6YS61] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Resetting the status of PersistedUpgradableObject: SPServer Name=D4P6YS61 Parent=SPFarm Name=STS_Config to Online.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: ReflexiveUpgrade [SPServer Name=D4P6YS61 Parent=SPFarm Name=STS_Config] failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Version string portion was too short or too long.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at System.Version..ctor(String version) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetVersionOnIisWebSite(Int32 iisInstanceId) at Microsoft.SharePoint.Upgrade.SPIisWebSiteSequence.get_BuildVersion() at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Resetting the status of PersistedUpgradableObject: SPFarm Name=STS_Config to Online.[SPManager] [INFO] [2/25/2007 10:29:52 PM]: Inplace Upgrade session finishes. root object = SPFarm Name=STS_Config, recursive = True. 6 errors and 0 warnings encountered.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Upgrade failed.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: Upgrade completed with errors. Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log. The number of errors and warnings is listed at the end of the upgrade log file.[SPManager] [ERROR] [2/25/2007 10:29:52 PM]: at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive) at Microsoft.SharePoint.StsAdmin.SPUpgrade.RunUpgrade(StringDictionary keyValues)Can anyone help me figure this out?
February 26th, 2007 9:48am

I have the exact same issue.Will continue to look around and post back here if I find the answerWaxhead
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2007 2:37am

I'm having the same error. Has anyone found a solution for this? Thx!
March 27th, 2007 11:41pm

Having the same error...and no luck googling, other than returning this forum post.
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2007 7:15pm

Hey there, I didn't find any help on the web, but I have got past these errors. The main things I found were having things like Other SharePoint sites on the server that were not really being used, and were casuing problems. So I removed all unwanted sites. Also, have a look at the log file, and paste in the errors you are getting. I had a bunch of other things I needed to fix, so I will take a look at your errors and will try and help u through them.
April 20th, 2007 12:39am

I had removed every site except the V3 admin and the shrepoint content site and still cannot get pass this error. I even try to run it ising psconfig.exe with no luck. I still can't find a solutuon for this and had to roll back to SP2003. Any one have suggestions on how to solve this?
Free Windows Admin Tool Kit Click here and download it now
May 1st, 2007 6:45am

I'm also having this problem... SBS 2003, WSS 2.0 - 3.0 upgrade with SQL 2000 back-end. Nothing online on how to fix it... anyone have any success with this?
August 8th, 2007 6:30am

dsstao wrote: I'm also having this problem... SBS 2003, WSS 2.0 - 3.0 upgrade with SQL 2000 back-end. Nothing online on how to fix it... anyone have any success with this?Nevermind, I ended up uninstalling it and reinstalling using the sharepoint.exe app and it fixed this. However, after installing and saying it was successful, there's absolutely no content. Thanks and FU Microsoft.
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2007 7:38am

I have the same issue... it seems many people are seeing this without anyone listening or looking into possible causes.
October 9th, 2007 7:40am

Hey there, I have gone through quite a few different size migrations and each posed there own issues (DAMIT). I found the best help was going through the Log File and Searching for ERRORthen working to resolve the errors that you find. If you need help in understanding what these error mean , please post them back here. A few timesthere have been just too many unknown issues to resovle and found it easier to just create a fresh install of wss 3.0, then migrating the lists and librarys as templates, then bringing the data across manually. I found it frustrating but it got the job done. I have also found that some sites that did go through thewss 2.0 to wss 3.0 upgrade,have had a few strange things going on with them and had to rebuilt parts of the site anyway. Highly customised sites can cause no end of problems, (e.g. custom codedpages, graphical customisations etc, and third party webparts). I am still required to upgrade the odd environment every now and then, and I now just think, if I can't get it sorted reasonably quickly, then time to start from scratch and install a fresh wss 3.0 site and work through a Template and Data Migration. That wayyou can at least see a definative goal line. I am receiving alerts on this post, so if you have some errors to post I will be happy to take a look. Good luck
Free Windows Admin Tool Kit Click here and download it now
October 9th, 2007 12:51pm

Good afternoon, I am havingissues withWindows SharePoint Services v3.0. I am unable to create a new web application or extend an existing web application. When I try to create a new web application or extend an applicaiton I get the following message: Version string portion was too short or too long. Please let me know if you have any ideas on what could be causing this. Thanks!
October 11th, 2007 12:56am

Is the SharePoint 3.0 a result of an upgrade from version 2.0? If so, is there any existing Web Applications that came accross with the upgrade that are working? I have nevercome accrossthis error before, maybe post it in the SharePoint Forums here (http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.setup_and_administration) and see if any of these guys have the answer. Else, if you can't get past this error, maybe you should backup all existing Web Applications, reinstall the SharePoint 3.0 from scratch and then restore your Web Applications. Sounds big, but doesn't that that long. But again, that forum that I suggested above is a really good place to get additional help.
Free Windows Admin Tool Kit Click here and download it now
October 11th, 2007 1:06am

Thanks for your help! I have been working on this issue for a while now and it happened about the same time as the security patch messed up the SharePoint Server on October 10th, 2007. This is not an upgrade from 2.0 to 3.0. Everything was working fine until I wasn't able to create a new site or site collection. I have 3 sites that are working but anything that I try to create on the server is blocked by this message: Version string portion was too short or too long.I am not able to get past this message to even try anything else. I am concerned about reloading this as I would like to spend some time making sure that it isn't something easy to fix.I am also receiving this error in my event viewer: The Execute method of job definition Microsoft.SharePoint.Administration.SPSqmTimerJobDefinition (ID ade089bf-2415-44eb-8394-2eea896b13af) threw an exception. More information is included below.Version string portion was too short or too long.Thanks for your help and suggestions!Thanks!
October 19th, 2007 5:39pm

I am having this error with Sharepoint 2010 as a new install. Did anyone ever answer this question?
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2010 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics