Upgrading from OCS2007R2 to Lync 2013

Folks,
We are looking to migrate our OCS 2007 R2 Enterprise, to Lync 2013.
We are running AD windows Server 2012 R2 functioanl level.
We have completed the schema,forest and domain prep for Lync 2013.
I have a few questions that you guys may be able to answer.
1.)
Can we upgrade from OCS 2007 R2 enterprise pool to LYNC 2013 standard pool.
2.)
Is there any concise documents out there that document how to upgrade form OCS 2007 R2 to Lync 2013.
Regards

Hi,
Migration of all Lync Server topologies and server roles is supported. You can migrate from one topology to a different topology, including from Standard Edition server to Enterprise
Edition server.
Click on the link below for more details,
Supported server migration paths and coexistence scenarios in Lync Server 2013
http://technet.microsoft.com/en-us/library/gg425764.aspx
Best regards,
Eric

Similar Messages

Migrate contacts from Skype to Lync 2013

Hi
Just need to get help for how to migrate contacts from Skype to Lync 2013 client ? Is there any special third party or Microsoft solutions to provide such service ?
Thanks
Regards
WenFei

Not possible and no third party that I am aware of.
JP
If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks.
Jean-Philippe Breton | Senior Microsoft Consultant | MCTS, MCITP, MCT, Lync MVP

Lync 2013 client is deployed but user accounts are not migrated from OCS to Lync 2013 Server - how to open Lync meetings automatically in the Lync Web Plug-in

We have in our enterprise the following scenario:
1 - Lync 2013 client is installed
2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
on the browser, using Lync Web Plug-in?

Thanks for the response,
First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue.

Upgrading AD Server for Lync 2013

I have now a Lync 2013 infrastructure deployed on an Active Directory infrastructure based on Windows Server 2003 including the servers, the domain functional level and forest functional level. We are planning to upgrade to Windows Server 2012.
My questions are:
1/ What are the impacts to my Lync 2013 infrastructure?
2/ Is there any documentation addressing the changes on the Lync Infrastructure in relation to AD upgrade?
3/ Anyone could share his/her experience?
Albert

Hi Albert,
Lync 2013 supports a domain functional level of Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or at least Windows Server 2003.
Hence when you introduce a Win2012 DC into the environment, it doesn't make any difference till you have the domain\forest Func Levels at Windows Server 2003.
Windows Server 2003 domain and functional levels of Active Directory are depreciated(soon to be removed) in Windows Server 2012 DC. So if you plan to remove the Windows 2003 and raise the FFL\DFL then you need to consider the questions you have
here.
What Happens Next?
Another common question: what impact does changing the Domain or Forest Functional Level have on enterprise applications like Exchange or Lync, or on third party applications? First, new features that rely on the Functional Level are generally limited to
Active Directory itself. Regardless, changing the Domain or Forest Functional Level should have no impact on an application that depends on Active Directory.
An application like Exchange uses Active Directory to store its objects, or to perform various operations, none of that functionality should be affected if the Domain or Forest Functional Mode changes. In fact, if your applications are also written to take
advantage of new features introduced in Active Directory, you may find that the capabilities of your applications increase when the Level changes.
The answer to the question about the impact of changing the Domain or Forest Functional Level is there should be no impact.
Lync 2013 FFL\DFL requirement
doesn't specify any additional features upon raising the levels beyond Win2003.
Just make sure you don't break the existing DC and have enough redundancy.
Supported in-place upgrade paths
Domain controllers that run 64-bit versions of Windows Server 2008 or Windows Server 2008 R2 can be upgraded to Windows Server 2012. You cannot upgrade domain controllers that run Windows Server 2003 or 32-bit versions of Windows Server 2008. To replace
them, install domain controllers that run a later version of Windows Server in the domain, and then remove the domain controllers that Windows Server 2003.
References:
https://technet.microsoft.com/en-us/library/gg412955(v=ocs.15).aspx
What is the Impact of Upgrading the Domain or Forest Functional Level?
Active Directory Domain Services support in Lync Server 2013
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Unable to call or receive call from contacts in Lync 2013 in Blackberry 10 OS

Hi,
I have installed apk file of Lync 2013 in my BB 10.
All features are working fine except the call part.
1. When I am making call (as Lync Call), the phone is trying to connect the contact but after two tries the call gets ended without connecting.
2. When someone is calling me thru lync and I am online in my mobile, the call is not coming to me, but a alert is showing as a text ping. Although the contact can hear the calling tune in his lync.
Please help.
Thanks in advance

From My understanding For Blackberry devices only Instant messaging is supported
via Enterprise Bes server product
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Can't move Users from On Premise Lync 2013 to Lync Online (Office 365)

Hi all
I try to move a single User from a local Lync Installation to Office 365 Lync. Everything is working locally, but in the Lync Powershell i face the following error:
The User with the following SIP-URI can't be found in the Active Directory. HostedMigration fault: Error = 201.
I didn't found anything on the web for the Error 201.
The User exists, and is synchronised with Azure AD eg Office 365. He has an E4 Plan.
Help would be very appreciated!

Hi,
Please check if the federation SRV record point to the local Edge Server.
Please make sure the Sign-on and directory synchronization works normally.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation package for Run-Time Engine 7.0

I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit). The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading. I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013. Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0. If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected). How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0? Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
Solved!
Go to Solution.

Bob_Schor wrote:
Are you running your VI from a Project? If so, you can look at Dependencies and get an idea what "dependent" VIs you might have. There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it. If all of your relevant VIs are in a single folder, add the entire folder. Now look in Dependencies.
BS
Yes I am running the VI from within a LV Project. After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
1. Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
2. Restart the PC
3. Open the project, close the project choosing to "save all"
4. Restart the PC
5. Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
6. Restart the PC
7. Open the project, close the project choosing to "save all"
8. Open the project and run the VI. No more messages about LabVIEW trying to find Run-Time Engine 7.0.

Quick way on upgrading from C# 2010 to 2013?

I'm using VC# 2010 with the .net micro framework installed. What's the easiest way to update to 2013 because I wanna update my netduino to 4.3.
David98xp

install VS 2013 and open your project, VS 2013 will convert your project and update it to new version of IDE.
Mark as answer or vote as helpful if you find it useful | Ammar Zaied [MCP]
And if your Netduino needs than a more current framework, go to
Project -> Project Properties -> and change there your framework.
Success
Cor

Since upgrade from Exchange 2007 to Exchange 2013 the conversations in Outlook do not group by subject

Hi Microsoft,
Since we have upgraded from Exchange 2007 to 2013 users complain their conversations in Outlook are no longer grouped based on the subject of an e-mail. I looks like Outlook uses other message properties for grouping e-mails in a conversation.
I have investigated all the forum topics and see that with exchange 2010 there is support added for the use of conversation-ID's. However the functionality to automatically group e-mails with the same subject in one conversation in Outlook is gone!
I would like to know if there is a fix to implement so that some our users get this functionality back. For Example: Let the exchange server not generate conversation-ID's and message-ID's for certain users.
Your help is greatly appreciated!

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Access is Denied -- Site Upgrade Upgrade from Foundation 2010 to Foundation 2013

I'm trying to do a Site Upgrade from Foundation 2010 to 2013 and I keep getting Access Denied during the site upgrade process
This is the error I keep seeing:
Inner Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Here is the log file.
"02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajyxw DEBUG [Navision] NeedsUpgrade = true, SchemaVersion = 4.0.25.0, TargetSchemaVersion = 15.0.30.0. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxmv DEBUG NeedsUpgrade [Navision] true because of upgrader [Microsoft.SharePoint.Upgrade.SPWebWssSequence] 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxmx DEBUG NeedsUpgrade [Navision] returned: True. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxn3 DEBUG Disposing Navision. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxni DEBUG Upgrading [Navision]. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajywv DEBUG Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.36 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence2 ajy8z DEBUG Begin upgrade of SPWeb scoped features. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1p DEBUG Template upgrade: Skipped upgrade WebTemplate XML for template 'STS#0' at: 'C:\Program Files\Common Files\Microsoft
Shared\Web Server Extensions\15\CONFIG\Upgrade\WssUpgrade.xml'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1t DEBUG Template upgrade:   Upgrade XML: <WebTemplate ID="1" LocaleId="*" FromProductVersion="4"
BeginFromSchemaVersion="0" EndFromSchemaVersion="2" ToSchemaVersion="3" /> 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1q DEBUG Template upgrade:   FromProductVersion '4' does not match current database version '3' for template 'STS#0'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1p DEBUG Template upgrade: Skipped upgrade WebTemplate XML for template 'STS#0' at: 'C:\Program Files\Common Files\Microsoft
Shared\Web Server Extensions\15\CONFIG\Upgrade\WssUpgradeB2B.xml'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1t DEBUG Template upgrade:   Upgrade XML: <WebTemplate ID="1" LocaleId="*" FromProductVersion="4"
BeginFromSchemaVersion="0" EndFromSchemaVersion="2" ToSchemaVersion="3" /> 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1q DEBUG Template upgrade:   FromProductVersion '4' does not match current database version '3' for template 'STS#0'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajy7f INFO Template STS#0: Web template upgrade for web/site [I deleted URL]6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajyw2 DEBUG SPRequest Objects=0 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajyw2 DEBUG SQL Query Count=0 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajyw2 DEBUG Execution Time=0.438254023905273 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajyxl INFO [Navision] IsBackwardsCompatible = False, CurrentVersion = 4.0.25.0, BackwardsCompatibleSchemaVersion = 15.0.30.0, TargetSchemaVersion
= 15.0.30.0. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxn1 DEBUG UPGRADE PROGRESS: current object = [Navision], current sequence = [SPWebWssSequence], action 1 out of total 14 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxn2 DEBUG UPGRADE PERCENTAGE: 5.21488095% done, Total Elapsed Time 00:00:08.8762641. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywc DEBUG Begin Initialize() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywd DEBUG End Initialize() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywe INFO Provision new master pages for O15 onto all webs and perform Visual Upgrade. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.37 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywf DEBUG Begin Upgrade() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:02.42 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajyqo INFO Modifying UIVersion field choices on the master page gallery in site: navision Site Url: [I
deleted URL]6052f9bdc7c9
02/28/2014 10:23:03.65 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajyqp INFO Provisioning seattle master page in site: navision Site Url: [I deleted URL]6052f9bdc7c9
02/28/2014 10:23:04.15 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUtility ajy0k INFO Master page 'seattle.master' already exists in the master page gallery, so there is no need to provision it. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:04.15 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajyqq INFO Updating masterpage in site: navision Site Url: [I deleted URL]6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajywk ERROR Action 15.0.3.0 of Microsoft.SharePoint.Upgrade.SPWebWssSequence failed. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajywk ERROR Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebWssSequence ajywk ERROR    at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)
at Microsoft.SharePoint.Library.SPRequest.OpenWeb(String bstrUrl, String& pbstrServerRelativeUrl, String& pbstrTitle, String& pbstrDescription, String& pbstrTitleResourceId, String& pbstrDescriptionResourceId, Guid& pguidID, DateTime&
pdtTimeCreated, String& pbstrRequestAccessEmail, UInt32& pwebVersion, Guid& pguidScopeId, UInt32& pnAuthorID, UInt32& pnLanguage, UInt32& pnLocale, UInt16& pnTimeZone, Boolean& bTime24, Int16& pnCollation, UInt32& pnCollationLCID,
Int16& pnCalendarType, Int16& pnAdjustHijriDays, Int16& pnAltCalendarType, Boolean& pbShowWeeks, Int16& pnFirstWeekOfYear, UInt32& pnFirstDayOfWeek, Int16& pnWorkDays, Int16& pnWorkDayStartHour, Int16& pnWorkDayEndHour,
Int16& pnMeetingCount, Int32& plFlags, Boolean& bConnectedToPortal, String& pbstrPortalUrl, String& pbstrPortalName, Int32& plWebTemplateId, Int16& pnProvisionConfig, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl,
String& pbstrThemedCssFolderUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl,
String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, UInt64& ppermMask, Boolean& bUserIsSiteAdmin, Boolean& bHasUniquePerm, Guid& pguidUserInfoListID, Guid& pguidUniqueNavParent, Int32& plSiteFlags,
DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange, String& pbstrWelcomePage, Boolean& pbOverwriteMUICultures, Boolean& pbMUIEnabled, String& pbstrAlternateMUICultures, Int32& plSiteSchemaMajorVersion, Int32& plSiteSchemaMinorVersion,
Int32& plSiteSchemaBuildVersion, Int32& plSiteSchemaRevisionVersion, Int32& puiVersion, Int16& pnClientTag, Boolean& pfIsEvalSite, Guid& pgSourceSiteId, DateTime& pdtExpirationDate, Guid& pgEvalSiteId, Guid& pguidAppProductId,
String& pbstrRemoteAppUrl, String& pbstrOAuthAppId, String& pbstrAppDatabaseName, Guid& pgAppDatabaseServerReferenceId, String& pbstrAppDatabaseTargetApplicationId, String& pbstrAppWebDomainId, Int32& plUpgradeFlags, DateTime&
pdtReminderDate, UInt64& pmaskDeny)     at Microsoft.SharePoint.SPWeb.InitWeb()     at Microsoft.SharePoint.SPWeb.get_Title()     at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId, Int32 mondoHint)
at Microsoft.SharePoint.SPWeb.<ClearMasterCssCaches>b__0()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated
secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPWeb.Update()     at Microsoft.SharePoint.Upgrade.VisualUpgradeAction15.Upgrade()     at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywl DEBUG Begin Rollback() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywm DEBUG End Rollback() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywp DEBUG Begin Dispose() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywq DEBUG End Dispose() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywr DEBUG SPRequest Objects=6 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywr DEBUG SQL Query Count=17 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade VisualUpgradeAction15 (15.0.3.0) ajywr DEBUG Execution Time=4867.40689109929 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR Upgrade [Navision] failed. Microsoft.SharePoint.Upgrade.SPWebWssSequence has the ContinueOnFailiure bit set. Moving
on to the next object in sequence. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR Inner Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR    at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)
at Microsoft.SharePoint.Library.SPRequest.OpenWeb(String bstrUrl, String& pbstrServerRelativeUrl, String& pbstrTitle, String& pbstrDescription, String& pbstrTitleResourceId, String& pbstrDescriptionResourceId, Guid& pguidID, DateTime&
pdtTimeCreated, String& pbstrRequestAccessEmail, UInt32& pwebVersion, Guid& pguidScopeId, UInt32& pnAuthorID, UInt32& pnLanguage, UInt32& pnLocale, UInt16& pnTimeZone, Boolean& bTime24, Int16& pnCollation, UInt32& pnCollationLCID,
Int16& pnCalendarType, Int16& pnAdjustHijriDays, Int16& pnAltCalendarType, Boolean& pbShowWeeks, Int16& pnFirstWeekOfYear, UInt32& pnFirstDayOfWeek, Int16& pnWorkDays, Int16& pnWorkDayStartHour, Int16& pnWorkDayEndHour,
Int16& pnMeetingCount, Int32& plFlags, Boolean& bConnectedToPortal, String& pbstrPortalUrl, String& pbstrPortalName, Int32& plWebTemplateId, Int16& pnProvisionConfig, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl,
String& pbstrThemedCssFolderUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl,
String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, UInt64& ppermMask, Boolean& bUserIsSiteAdmin, Boolean& bHasUniquePerm, Guid& pguidUserInfoListID, Guid& pguidUniqueNavParent, Int32& plSiteFlags,
DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange, String& pbstrWelcomePage, Boolean& pbOverwriteMUICultures, Boolean& pbMUIEnabled, String& pbstrAlternateMUICultures, Int32& plSiteSchemaMajorVersion, Int32& plSiteSchemaMinorVersion,
Int32& plSiteSchemaBuildVersion, Int32& plSiteSchemaRevisionVersion, Int32& puiVersion, Int16& pnClientTag, Boolean& pfIsEvalSite, Guid& pgSourceSiteId, DateTime& pdtExpirationDate, Guid& pgEvalSiteId, Guid& pguidAppProductId,
String& pbstrRemoteAppUrl, String& pbstrOAuthAppId, String& pbstrAppDatabaseName, Guid& pgAppDatabaseServerReferenceId, String& pbstrAppDatabaseTargetApplicationId, String& pbstrAppWebDomainId, Int32& plUpgradeFlags, DateTime&
pdtReminderDate, UInt64& pmaskDeny)     at Microsoft.SharePoint.SPWeb.InitWeb()     at Microsoft.SharePoint.SPWeb.get_Title()     at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId, Int32 mondoHint)
at Microsoft.SharePoint.SPWeb.<ClearMasterCssCaches>b__0()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated
secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPWeb.Update()     at Microsoft.SharePoint.Upgrade.VisualUpgradeAction15.Upgrade()     at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR Exception: Action 15.0.3.0 of Microsoft.SharePoint.Upgrade.SPWebWssSequence failed. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object
o, Boolean bRecurse) 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnn DEBUG Elapsed time upgrading [Navision]: 00:00:04. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxn6 DEBUG Disposing Navision. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxp7 DEBUG Found subweb template STS#0 (lcid: 1033) for ContentDatabase WSS_Content. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxmf DEBUG CanUpgrade [Customer Service Team] returned: True. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnh DEBUG Customer Service Team IsGrown=False IsRoot=False IsLeaf=True. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxmf DEBUG CanUpgrade [Customer Service Team] returned: True. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajy68 DEBUG Loading onet.xml at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\SiteTemplates\STS\xml\onet.xml 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPWebTemplateSequenceForWeb ajy7b DEBUG Template STS#0: Calculated a target template version of '15.0.0.3' with target compatibility level of '15'
for the 'STS#0' template. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1p DEBUG Template upgrade: Skipped upgrade WebTemplate XML for template 'STS#0' at: 'C:\Program Files\Common Files\Microsoft
Shared\Web Server Extensions\15\CONFIG\Upgrade\WssUpgrade.xml'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1t DEBUG Template upgrade:   Upgrade XML: <WebTemplate ID="1" LocaleId="*" FromProductVersion="4"
BeginFromSchemaVersion="0" EndFromSchemaVersion="2" ToSchemaVersion="3" /> 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1q DEBUG Template upgrade:   FromProductVersion '4' does not match current database version '3' for template 'STS#0'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1p DEBUG Template upgrade: Skipped upgrade WebTemplate XML for template 'STS#0' at: 'C:\Program Files\Common Files\Microsoft
Shared\Web Server Extensions\15\CONFIG\Upgrade\WssUpgradeB2B.xml'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1t DEBUG Template upgrade:   Upgrade XML: <WebTemplate ID="1" LocaleId="*" FromProductVersion="4"
BeginFromSchemaVersion="0" EndFromSchemaVersion="2" ToSchemaVersion="3" /> 42b4789c-6c14-203b-54a5-6052f9bdc7c9
02/28/2014 10:23:07.24 OWSTIMER (0x0678) 0x0A50 SharePoint Foundation Upgrade SPXmlConfiguration ajy1q DEBUG Template upgrade:   FromProductVersion '4' does not match current database version '3' for template 'STS#0'. 42b4789c-6c14-203b-54a5-6052f9bdc7c9"

do you have the any no access / locked sites in that database and also any site which exceed its quota.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Excel file error after upgrade from 2010 to 2013

Hi there,
I did the upgrade from 2010 (Enterprise) to 2013. The excel files are not opening giving error.
ULS Log: "Unexpected error when trying to access service settings in the configuration database. Make sure the proxy for this service application is a member of the default proxy group for the active web application. Error = ExcelServerWebServiceApplication.Local:
Could not get the web application associated with this context. This indicates that the Excel Server service is not properly registered or provisioned.."
Question : Do I need to create New Excel Service Application separately on SharePoint 2013 Server?
I followed this link for upgrade
http://technet.microsoft.com/en-us/library/jj839719.aspx but it doesn't say anything for Excel SA.
Note: I have plan to configure separate Office APP Server to give user access the documents on iPad/iPhone. Should I need to do any configuration related to this error on Office App Server?
Please advice.
Thanks,
Khushi

Hi Khushi ,
Yes, you need to create New Excel Service Application separately on SharePoint 2013 Server. Due to only the following service applications have databases that can be upgraded when you upgrade from SharePoint
Server 2010 to SharePoint Server 2013:
Business Data Connectivity service application
Managed Metadata service application
PerformancePoint Services service application
Search service application
Secure Store Service application
User Profile service application
Attaching and upgrading these databases configures these service applications. Settings for other services will have to be reconfigured when you upgrade.
Reference:
Services upgrade overview for SharePoint Server 2013
For configuring Office Web Apps Server , you can refer to the blog:
http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
Best Regards,
Eric
Eric Tao
TechNet Community Support

Expiration date not displaying after upgrade from 2007 to 2013

I recently upgraded from MOSS 2007 to 2013. I have information management set up on a library of InfoPath forms. For the forms that were created prior to the upgrade, the expiration date is displaying and actually get updated if I modify them.
But none of my forms that have been created after the upgrade, are displaying when the expiration date is, which should be one year from modify date. If I modify the forms created prior to the upgrade, they reflect the new, update date.
Are these new forms not getting the policy applied to them, and why not? I am not sure why the older forms are getting updated, but not my new ones.
Denise E.

Hi Denise,
According to your description, my understanding is that the Expiration date column was not displaying values after upgrading from SharePoint 2007 to SharePoint 2013.
Per my knowledge, we can only use the date column which is added to the library or list or the Declared Recorded date to set the retention policy, so if the Expiration date is used in the retention policy then the Expiration date should be a column in the
library or list.
I recommend to check the retention policy in the library and see which column is used in the retention policy as the image below shows:
After that, go to the Library settings to find this column.
Could you please provide screenshots of the retention policy and the columns in the Library settings page?
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Just moved from in house ocs 2007 R2 to office 365 lync 2013, I'm clear to "unprep" right?

We've just migrated from in house ocs 2007 r2 to office 365 w lync 2013. We are using dirsync to sync our AD with o365.
We'd like to decommission our OCS 2007 server since its no longer being used. Will running unprep impact our hosted lync 2013 setup given that we are using dirsync? I don't think it should, but just want to confirm.
Any advice appreciated.

Hi MC625,
In my opinion, unprep is not necessary and I suggest you should not perform this action.
I haven't seen an unprep referenced in the migration from OCS to Lync 2013 articles.
https://technet.microsoft.com/en-us/library/jj205375%28v=ocs.15%29.aspx
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Move Users from OCS 2007 R2 to New Lync 2013

I am trying to move users from OCS to Lync 2013 from within the Lync 2013 Control Panel and am getting an error that states "Cannot find Registrar pool. Verify that "FQDN of old pool" is a valid registrar pool.

Give this Lync powershell command a go:
Move-CsLegacyUser <user> -Target <Lync2013 Pool Name>
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
Have you reviewed the OCS to 2013 migration documents?
http://technet.microsoft.com/en-us/library/jj205375.aspx
Did you add the OCS pool to the 2013 topology?
Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

Upgrading from Project Server 2010 to 2013 ConvertTo-SPProjectDatabase gives error (Convertto-SPProjectDatabase : Action 15.0.38.0 of Microsoft.Office.Project.Server.Upgrade.PublishedDatabaseSequence)

Getting the error on subject line when I try to upgrade from Project 2010 to 2013

Hi,
Do you get and error when the command is executed or when you try to start the execution (the command is not valid)?
If you get the error when you try to start the execution, I would suggest re-typing the command and make sure all parameters are valid.
Please give us the error details if you get the error when the command is running
Paul

Upgrading from OCS2007R2 to Lync 2013

Similar Messages

Maybe you are looking for