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: System....


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

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

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

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

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

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

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 ...


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

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

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

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

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

While recommended to install security updates as soon as possible, you will need to evaluate the security risk of not installing a particular security patch. This is something we will not be able to help you with. You do not need to install the Cumulative Update if you do not wish to install it. Yes, some non-CUs increment the farm build number due to an ...


3

I would expect it to work, but you have some interesting variables there so it would be a good idea to plan for some validation before you commit to anything. Normally there is some backwards compatibility with office apps. InfoPath is a little different, but the underlying XML schema should be compatible.


3

Here are a few resons on why to upgrade Upgrade to SQL Server 2008 R2 - performance and availability SQL Server 2005 mainstream support will end fairly soon (read more at http://support.microsoft.com/gp/lifesupsps) Security Better Reporting Services


3

Miroslaw. What you are asking is not a question with one easy answer. I would first suggest that you learn about the WSS 2.0 installation that you have, and how you can do effective backup and restores. More info on WSS 2.0 can be found here. Then you need to look at the upgrade path and what 'gotchas' to look for. It is not a trivial process to upgrade,...


3

You could also temporarily change the DNS to point to another server during the upgrade process. Make sure that you lower the TTL of the DNS records so that you quickly can switch back.


3

Enumallwebs should list the sites that are orphaned too, so it is weird it fails! Did you prepare for your upgrade properly by doing PreUpgradeCheck, and resolve all issues? Did you do enumallwebs on the site before upgrading? Orphans should be deleted before attempting an upgrade rather than after... Make sure you read up on the new tools for preparing ...


3

Farm Administrators do not by default have access to Site content. Site collection feature upgrade and activation is normally delegated to the Site Collection Administrators (I think).



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