Tag Info

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


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

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


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

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

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


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


4

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)


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.


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: http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb267377.aspx Then you need to look at the 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

You are currently at Service Pack 2, which is good. The Cumulative Updates address issues that you may have experienced. You should only apply the Cumulative Updates in production if you are experiencing the issue that the CU addresses. That said, the CUs do contain previous CUs, so if you want to apply only the most recent, you will recieve the fixes in the ...


3

We recently did this and it was a bit of a nightmare. Keep in mind that we were dealing with a really screwed up 2007 instance to begin with and that we were in the 1 terabyte range rather than 5 gigabytes. I doubt your migration will be as difficult as ours. There are too many points to hit regarding migration to cover in one post so I will direct you to ...


3

Your IVersioningPersonalizable code looks right, but I think SharePoint determines unknown properties by their name, and if property was not renamed - it will not be unknown... So, could you please rename YSeriesType property and try to perform the upgrade again?


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

Did you manually add that link? Looks like the only viewlsts.aspx I can find resides directly in the /_layouts/ directory. It's possible that the old viewlsts.aspx was localized and was replaced in 2010 by a generic viewlsts.aspx containing resource strings.


3

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

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



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