Hot answers tagged

9

If the WSP has any assemblies in it - no. The assemblies developed for SharePoint 2010 will be referencing the SharePoint 2010 core assemblies, and will fail when trying to load them in SharePoint 2007. If the WSP only has XML in it, and no server side code in assemblies, it should deploy fine, given it has no Feature code that's new in 2010 (such as ...


7

As the documentation states, when you add new artifacts to a solution you need to reinstall it. Really nothing new here, except for support for solution dependencies (and this is really only half implemented, since you can delete solutions that other solutions depend upon without getting any warning) Feature upgrade is an entirely different matter. No ...


7

You can use same url or change the URL at the destination farm. If you use the old url, only thing it will take time when you point your DNS to new servers. If you use new url: People who bookmarked the old url will see the difficulites if some site collections hardcoded url they will upset or if you have custom app which use the hardcoded url then they ...


6

Run the Get-SPFeature Powershell against your 2007 environment and it'll kick out a list of all of your features resolving the GUIDs to the names. Powershell Commands to List SharePoint Features To James' point, it sounds like you missed a step or two in your upgrade planning. Make sure you're running Test-SPContentDatabase before you kick off the actual ...


6

Looks like you're using default Update method of SPContentType when updating your content type in feature updating receiver. To push changes to all inherited list content types, you should use another overload of the Update method, and pass true to it: contentType.Update(true); Description of the parameter from MSDN: updateChildren Type: ...


5

You could loop through all the existing sub-sites with a PowerShell script, and use the feature cmdlets to activate the feature on existing sites. Using this method you could also insert some logic/conditions to enable or not enable the new feature if that is useful.


5

You can continue creating your Web Parts as you are now. As long as you are not using any known deprected method in the SharePoint OM then you are fine. There are no breaking changes in Web Part development, more like enhancements that you can take advantage of in SP2010. My guess is that you have seen the Visual Web Parts and there is no way to convert a ...


5

I should have checked this earlier. I made 2 empty SharePoint projects. One 2010 and one 2013 and did a compare of the different files. The only difference i could find was in the csproj file. In the SP 2013 project there is a <TargetOfficeVersion>15.0</TargetOfficeVersion> property that was not present in the SP 2010 project. I added it and ...


5

Yes, Service Pack 2 contains all Cummulative Updates and Hot fixes before it.. including SP1 Install SharePoint 2010 Service Pack 2 the right way SharePoint Server 2010 Service Pack 2 has been released (Updated July 31st, 2013)


5

When you create a new web application, the content database associated with it is fresh in the sense that you haven't added any data to it yet. The purpose of upgrading from SP 2010 to SP 2013 is to carry over the content from SP 2010 to SP 2013. So you delete the original content database as you don't need it and attach the content database from SP 2010 to ...


4

Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms. However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.


4

We upgraded one of our 225GB content databases in roughly 4 hours so 4 days is excessive. What this actually sounds like is that one of the servers in the mix is running into severe resource issues and is having to swap to disk a lot more than it should. I'd check all the servers in the farm including the SQL server and make sure that they have adequate ...


4

The search database is not a content database. You need to upgrade using the SharePoint 2010 Farm Configuration Wizard. I would run that and see where it gets you and then you can find any errors in the upgrade logs. Here is a link to help. http://www.justanothertechnologyguy.com/2011/11/databases-require-upgrade-or-not.html Excerpt: •Open a command ...


4

I had the same problem when running IE on the server and opening the Central Admin URL. Went to all Programs/Microsoft SharePoint 2010 Products/SharePoint 2010 Central Administration and ran that as an Administrator and had no problems adding users. I was also able to add users when I used a workstation to add users via the URL.


4

When you install the executable for a Cumulative Update (CU), you have not actually upgraded your servers yet. The PSConfig.exe (Command Line), or the SharePoint Products Configuration Wizard (GUI), will need to be run to upgrade both the running binaries, and make any changes to the SharePoint database schemas provided in the CU. In this case, you have the ...


4

If all requests go through a proxy server, and your proxy server supports this, create a rule that redirects all traffic for the web application, not just the entire domain, to a new temporary web page. You can also take the low tech route and announce the change to your users by email.


4

Or another option is to create a simple html page called App_Offline.htm and put it in the root of the virtual directory. No matter what page is hit, this page gets rendered. When you're done simply delete/nename it. I've only done this before for ASP.NET but it should work for SharePoint as it is build on top off asp.net. Must be .net 2.0 though. Now if ...


4

The upgrade should allow the current SPD workflows to function normally, however, any URLs that are not relative links will be the items that will not function properly with an upgrade that changes the URL. IDs on lists should stay the same.


4

First a shameless plug to my own whitepaper on upgrading SharePoint from 2007 to 2010 ;-) Joel Oleson had a book planned (that included chapters in my whitepaper), but I think it was delayed. You can access parts of it for free for 45 days here. In the meantime check his blog. You should also check the planning guidance on TechNet. Also SharePoint 911 ...


4

Start by ensuring new hardware is 64-bit. Deploying 64-bit is our current best practice recommendation for SharePoint 2007. Deploy Service Pack 2 and take a good look at the SharePoint 2010 Upgrade Checker that’s shipped as part of the update. The Upgrade Checker will scan your SharePoint Server 2007 deployment for many issues that could affect a future ...


4

That error can be caused by a lot of things, e.g.: service accounts with invalid passwords missing feature dependencies missing content databases lack of permissions of your account the user account control (UAC) on the server (eventhough you should see a "access denied" error) a previous unfinished upgrade process any many more... I recommend rebooting ...


3

This issue keeps cropping up. To recap, the best way to do get a quick view of what is being used where in a given content database is with the stsadm command enumallwebs using the addtional parameters (supplied with the October 2009 Cumulative Update, if you are using SP2007): stsadm -o enumallwebs -includefeatures -includewebparts -includeeventreceivers ...


3

you can use command "net start sptimerv4" in command window when the wizard is starting phase 9/10, then you can see it's work fine!


3

I'll be the first here to say it. It depends Shelling out for the features to "possibly" take advantage of them, without any concrete plans to actually use them is a project doomed to failure. If you're unsure yet what you'll take advantage of, get the Information Worker VHD and have a play around, build a showcase environment to get buy-in for the ...


3

I had the same errors. Detaching databases didn't help, it was for some reason, the langue packs that were bugging me. After deinstalling the language packs, and running PSconfig again, my upgrade finished! correct upgrade order (In my opinion ;). some people think different about the subject): install SP1 - foundation install SP1 - Server psconfig ...


3

It appears that when you created the new web application and database that it is already attached. If that is the case, then running the command will fail, you cannot add a content database that is already added. To check to see if this is the case, you can go into Central Adminsitration and view the content databases that are attached to the web ...


3

One of the first steps to any upgrade is to perform the Test-SPContentDatabase check against every content database in the farm. If this check finds errors, your upgrade will not complete successfully. There's no way around this; if you want a successful upgrade, you must pass both the stsadm preupgradecheck and Test-SPContentDatabase. If the errors are ...


3

You cannot install SharePoint 2010 WSP on a SharePoint 2007 environment, because it references the SharePoint 2010 DLL files and the package Product Version is set to 14.0. If you got the visual studio project, you could try and downgrade the project so that it works for 2007. More information about this can be found on this blog post.


3

There is no such thing as a "typical" upgrade from 2007 to 2010. Here are some starter questions that should point you to an answer: Is this 2007 WSS out of the box with no customizations or is it MOSS 2007 heavily customized with deep ties to other systems via the BDC? Are they using any of the "Fab 40" templates? How much data is this? How much custom ...



Only top voted, non community-wiki answers of a minimum length are eligible