DPm 2012 r2 problem after moving Sharepoint 2013 to a differnt SQL using another alias

Hi,
I have resently installed DPM 2012 r2 and I want to backup my Sharepoint 2013 farm. I can install the client on Sharepoint server and the SQL server. This is a new protection and I have earlier moved the Sharepoint 2013 farm to a different SQL server
not with the same name using the SQL alias method.
When I try to create a Sharepoint backup I get the old SQL server name and error to check the SQL wss is running. The wss is running and the DPM user is local admin and sysadmin og the new SQL server. I added in hosts the old SQL server name
pointing to the new sql server ip address.
I need to know if this is doable in DPM or must I do something else?
thanks.
Erró

Here is the information you needed.
* WRITER "SharePoint Services Writer"
- Writer ID = {da452614-4858-5e53-a512-38aab25c61ad}
- Writer instance ID = {b8787079-eacd-4ced-9c7d-1e9aa5ac240a}
- Supports restore events = TRUE
- Writer restore conditions = VSS_WRE_ALWAYS
- Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
- Requires reboot after restore = FALSE
- Excluded files:
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Config"
- Name: AVA_SP2013_Config
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Config
- Caption: Configuration Database AVA_SP2013_Config
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Config"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_State_Svc"
- Name: AVA_SP2013_State_Svc
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_State_Svc
- Caption: Generic Database AVA_SP2013_State_Svc
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_State_Svc"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Heimar"
- Name: AVA_SP2013_Content_Heimar
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Heimar
- Caption: Content Database AVA_SP2013_Content_Heimar
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Heimar"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Wiki"
- Name: AVA_SP2013_Content_Wiki
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Wiki
- Caption: Content Database AVA_SP2013_Content_Wiki
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Wiki"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
- Name: AVA_SP2013_Content_ActiveProjects
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects
- Caption: Content Database AVA_SP2013_Content_ActiveProjects
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite"
- Name: AVA_SP2013_Content_Mysite
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite
- Caption: Content Database AVA_SP2013_Content_Mysite
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite1"
- Name: AVA_SP2013_Content_Mysite1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite1
- Caption: Content Database AVA_SP2013_Content_Mysite1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite2"
- Name: AVA_SP2013_Content_Mysite2
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite2
- Caption: Content Database AVA_SP2013_Content_Mysite2
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite2"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite3"
- Name: AVA_SP2013_Content_Mysite3
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite3
- Caption: Content Database AVA_SP2013_Content_Mysite3
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite3"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite4"
- Name: AVA_SP2013_Content_Mysite4
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite4
- Caption: Content Database AVA_SP2013_Content_Mysite4
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite4"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
- Name: AVA_SP2013_SharePoint_Admin_Content
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content
- Caption: Content Database AVA_SP2013_SharePoint_Admin_Content
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
- Name: AVA_SP2013_Secure_Store_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB
- Caption: Generic Database AVA_SP2013_Secure_Store_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
- Name: AVA_SP2013_PerformancePoint Service Application
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application
- Caption: Generic Database AVA_SP2013_PerformancePoint Service Application
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Managed Metadata Service"
- Name: AVA_SP2013_Managed Metadata Service
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Managed Metadata Service
- Caption: Generic Database AVA_SP2013_Managed Metadata Service
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Managed Metadata Service"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Word_Automation"
- Name: AVA_SP2013_Word_Automation
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Word_Automation
- Caption: Generic Database AVA_SP2013_Word_Automation
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Word_Automation"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Profile DB"
- Name: AVA_SP2013_Profile DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Profile DB
- Caption: Generic Database AVA_SP2013_Profile DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Profile DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\Sync DB1"
- Name: Sync DB1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\Sync DB1
- Caption: Generic Database Sync DB1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\Sync DB1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Social DB"
- Name: AVA_SP2013_Social DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Social DB
- Caption: Generic Database AVA_SP2013_Social DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Social DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_BDC_Service_DB"
- Name: AVA_SP2013_BDC_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_BDC_Service_DB
- Caption: Generic Database AVA_SP2013_BDC_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_BDC_Service_DB"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
- Name: Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Caption: OSearch Administration Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
- Name: Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Caption: OSearch Crawl Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
- Name: Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Caption: OSearch Analytics Reporting Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
- Name: Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Caption: OSearch Links Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
- Name: IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Caption: OSearch15 Content Index Catalog_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{0ff1ce15-0201-0000-0000-000000000000}:\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
Erró

Similar Messages

Error in Configuration Wizard after installing SharePoint 2013 Service Pack 1

Windows Server 2012 with latest updates and SharePoint 2013 with latest updates:
I installed SharePoint 2013 Service Pack 1 and when I run the configuration Wizard i get this error:
Error in Configuration Wizard
Resource id to be retrieved is PostSetupConfigurationFailedEventLog for language English (United States)
Resource retrieved id PostSetupConfigurationFailedEventLog is Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information
located at {0}, fix the problem, and run this configuration wizard again.
Leaving function StringResourceManager.GetResourceString
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_55_49_686_1872915373.log, fix the problem, and run this configuration wizard again.
In event view I see this two errors:
1) First error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
104
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135580
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Failed to initiate the upgrade sequence. An exception of type System.MissingMethodException was thrown. Additional exception information: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object,
System.String, Microsoft.SharePoint.Upgrade.SPLog)'. System.MissingMethodException: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object, System.String, Microsoft.SharePoint.Upgrade.SPLog)'. at System.RuntimeTypeHandle.GetTypeByName(String
name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError,
Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) at System.Type.GetType(String typeName) at Microsoft.SharePoint.Utilities.SPTypeSerializer.DeserializeType(String typeName,
Guid classId, Boolean bResolveMissingTypes) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.ResolveObjectAndClassVersions(SPLog log) at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
2) Second error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
100
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135581
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_41_9_710_572545016.log, fix the problem, and run this configuration wizard again.
Please advise on next steps.
How can I successfully install SP1?
Thanks,
Alex

could you please share the upgrade log file, so that we understand the error?
did you reboot your server after the installation of SP1?
also try to clear the Config cache on the servers and then try again?
you can run this command on the server its failing
Get-SPProduct -local
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
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

Backup Sharepoint 2013 SP1 Farm with SQL 2014 RTM "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
Igor

This is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL 2012 AlwaysON High Availability for SharePoint 2013

Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
We got one more Server & we don't have Storage so need to configure Always On.
There are Some Confusions:
1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
2- What are the Changes need to be done on Production Server?
3- What are the Steps to be followed While Configuring new Database Server?
Regards,

Hi Genius1985,
According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
to the following article:
http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012. This needs to be done on all of the SQL Server instances that we will configure as replicas in our
Availability Group.
For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li

TypeLoadException after install SharePoint 2013 Service Pack 1

After install SharePoint 2013 Service Pack 1 Russian I got the following error (approximate translation from Russian):
TypeLoadException: Method 'Upgrade' does not implemented in 'WorkflowServiceApplicationProxy'
Any ideas how to workaround it?

Hi,
Please post your ULS logs here.
Please remember to click 'Mark as Answer' on the answer if it helps you

How to Insert Sharepoint 2013 Person or Group Field using VBA

Hello,
How to Insert Sharepoint 2013 Person or Group Field using VBA , I tried set the field with ID / ID;Name / Name
but all failed, Please advice
Function SetSP_Field(F_Yer As Single, F_WekNo As Single, F_ProjectNum As String, strField As Variant, strFieldValue As Variant) As String
' test code
    Dim rst         As Recordset
    Dim strSQL      As String
    Dim SP_RecSet   As ADODB.Recordset
    Set SP_RecSet = New ADODB.Recordset
    SetSP_Field = False
    strSQL = "Status Report"
    On Error Resume Next
    Call SP_Connect(2)
    strSQL = "select " & SP_List & ".* From " & SP_List _
           & " Where [Year] = " & CInt(F_Yer) _
           & "   and [WeekNo] = " & CInt(F_WekNo) _
           & "   and [Compass_Code] = '" & F_ProjectNum & "' ; " _
'           & " Set " & strField & " = " & strFieldValue
    'Debug.Print strSQL
    'Debug.Print SP_CN
    SP_RecSet.Open strSQL, SP_CN, adOpenStatic, adLockOptimistic
    If SP_RecSet.RecordCount = 0 Then
        Debug.Print "Record for project: " & F_ProjectNum & " not found"
        LogFile.WriteLine ("Record " & strID & " not found")
    End If
    If Not SP_RecSet.EOF Then
        'SP_RecSet.Edit
        SP_RecSet.Fields(strField) = strFieldValue
        SP_RecSet.Update
        If Err.Number <> 0 Then
            MsgBox ("SP Update Error: " & Err.Description)
            GoTo Exit_Fun
        End If
        SetSP_Field = True
    End If
Exit_Fun:
    SP_RecSet.Close
    Set SP_RecSet = Nothing
End Function

Hi Tim,
Let’s verify the followings:
Whether this issue occurred for other lists in the same site.
Whether this issue occurred for all users who don’t have full control.
Whether this issue occurred on other sites.
When you created the people & group column, which show field did you used? Please try to use a different show field for the people & group column, compare the result.
In addition, please check if the link is useful:
http://www.learningsharepoint.com/2013/08/21/empty-value-in-people-picker-after-saving-the-list-form-in-sharepoint/
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Javascript error after last sharepoint 2013 update : unable share single list element

After yesterday update of SharePoint 2013 using Windows update we receive a JavaScript error when we try to share a single list element. Our IE is Italian the error is "Properties or field not inizialized"
This is the user interface "hanged" and wait ....
The problem not exist if we share an entire list or website.
LSo Lorenzo Soncini Trento TN - Italy

Hi Lorenzo,
Glad that you solved the issue and thanks for sharing, this will benefit others who have similar issue.
Regards,
Daniel Yang
TechNet Community Support
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]

Could not start IIS after installing SharePoint 2013 Sep CU?

Hi All,
Recently I installed SharePoint 2013 Sep CU. Everything went well; I was able to install it and run the configuration wizard successfully but after that IIS was stopped and was not able to start because WWW Publishing service was stopped.
When I tried to start that service, it gives below error. Event Viewer did not show anything specific. Please guide me on this issue.
Appreciate your help.
Thanks,
Rahul Babar
ASP.NET, C# 4.0, Sharepoint 2007/2010, Infopath 2007/2010 Developer http://sharepoint247.wordpress.com/

Hi Rahul,
Please restart your machine, compare the result.
And please double click on the “World Wide Web Publishing Service”, in the top we can be able to see the “dependency” option, make sure all these dependencies are started.
In general, this issue is caused because The Remote Procedure Call (RPC) Service is not installed. All of the IIS services depend on the RPC Service.
Additionally, if the TCP/IP protocol is not installed, the same symptoms result.
More information, please refer to the links:
http://support.microsoft.com/kb/155768
http://www.dotnetsharepoint.com/2015/01/the-world-wide-web-publishing-service.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

DPM 2012 R2 Crashes after upgrade - Tape Backup

Hello guys,
I have recently upgraded from DPM 2012 SP1 to DPM 2012 R2 Rollup 3 on Windows 2012 R2 (in-place upgrade)
The basic procedure was to backup the DB, uninstall DPM, install DPM 2012 R2, restore the DB. re-sync all the inconsistent replicas and upgrade server agents. When it comes to the offsite tape backup for whatever reason every time the tape backup
commences it fails instantly with the below error and reports "Backup to Tape Failed"
"Event Log shows MSDPM Error ID 945"
It appears to be failing due to a missing stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'. The stored procedure does not exist on other DPM servers. I'm guessing this is something hanging around in the DB from prior to the upgrade but I can't
seem to track it down. Does anyone have any ideas upon how to resolve the issue?
The description for Event ID 945 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Unable to connect to the DPM database because of a general database failure. Make sure that SQL Server is running and that it is configured correctly.
Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>84123</Seq><TimeCreated>25/10/2014 23:01:01</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlException</ExceptionType><ExceptionMessage>Could
not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.</ExceptionMessage><ExceptionDetails>System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.
   at Microsoft.Internal.EnterpriseStorage.Dls.SummaryManager.SummaryManagerMachine.OnStart(ErrorInfo& eInfo)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.SimpleStateMachine.Start(Message msg)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Engine.ChangeState(Message msg)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.TaskInstance.Process(Object dummy)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.FsmThreadFunction.Function(Object taskThreadContextObj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
ClientConnectionId:fbd15cf8-5b7b-4438-befe-a3a54426d371</ExceptionDetails></FatalServiceError>

For this issue, you can refer below link
http://blogs.technet.com/b/dpm/archive/2012/01/30/fix-the-dpm-console-crashes-and-logs-event-id-945-when-making-any-changes.aspx
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

DPM 2012 R2 Crashes after upgrade.

I recently upgraded from DPM 2012 SP1 to DPM 2012 R2 Rollup 2. The basic process was to backup the DB, uninstall DPM, upgrade the OS from 2008 R2 to 2012. Reinstall DPM 2012 SP1, restore the DB making sure everything works and then upgrade to
DPM 2012 R2. I did this on my primary server first which originally seemed to work well and then followed up on my secondary server. For whatever reason I had trouble on the secondary and ended up installing DPM clean on a new os and that server is working
perfectly. On my primary however I am getting the following error 1 time each day.
Event Log shows MSDPM Error ID 945
It appears to be failing due to a missing stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'. The stored procedure does not exist on either of my DPM servers. I'm guessing this is something hanging around in the DB from prior to the upgrade but
I can't seem to track it down.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING No retry on exception System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1
wrapCloseInAction)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,
Boolean asyncClose)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader
dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String
resetOptionsString)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior,
Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior,
Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName,
Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlRetryCommand.ExecuteNonQuery()
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING ClientConnectionId:da1c0341-89eb-4873-9852-b882daff9e5c
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Error = 2812
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Index #0
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Source: .Net SqlClient Data Provider
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Number: 2812
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING State: 62
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Class: 16
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Server: tcp:QUIMBY\MSDPM2012
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Message: Could not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Procedure:
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING Line: 1 FileName:; Method:ComputeStatistics(); lineNo:0; ilOffset:227.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:ComputeDailyStatistics(); lineNo:0; ilOffset:37.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:OnStart(); lineNo:0; ilOffset:67.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:Start(); lineNo:0; ilOffset:2.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:ChangeState(); lineNo:0; ilOffset:67.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:Process(); lineNo:0; ilOffset:503.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:Function(); lineNo:0; ilOffset:29.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:RunInternal(); lineNo:0; ilOffset:112.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:Run(); lineNo:0; ilOffset:4.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem(); lineNo:0; ilOffset:0.
0E80 1878 07/09 05:00:07.555 09 Catalog.cs(1010)  194D6C88-C8CA-4B3C-9BD8-CD389A51E6DE WARNING FileName:; Method:Dispatch(); lineNo:0; ilOffset:162.
Erick-W

For this issue, you can refer below link
http://blogs.technet.com/b/dpm/archive/2012/01/30/fix-the-dpm-console-crashes-and-logs-event-id-945-when-making-any-changes.aspx
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Need to know how to allow mail to be sent to my Hosted Sharepoint 2013 site's documents folder/ Using CRD 7 reporting

I have gotten as far as adding a new app, naming the folder and going into CRD, for the report we need online and attempted to enter the settings information for our sharepoint site. The issue is no matter how I enter the credentials it will not authorize
and finish the connection. We have tried a couple of different things when it comes to the user name and domain line. we tried:
corporate\username;
corporate-traffic.com\username;
[email protected]..
we are trying to figure out the correct way to enter this information, mainly what the domain name should be since Sharepoint 2013 is all cloud based.
My issue is when I get to entering credentials none of my admins credentials work... I think it may be the domain name that is throwing it off. I keep getting the error: server was unable to process request ---> Access is denied. (Exception
From HRESULT: 0x80070005 ((E_ACCESSDENIED))
So can anyone point me in the right direction to fix this error and enable the report to email to my sharepoint site documents folder?
Just to clarify...
I need the correct domain info per office 365's Sharepoint to enter the info into our report options on CRD seven report. And how we can enable SMTP to our documents folder on our SharePoint site.

I asked Christian Steven's Support staff about this and they came out with a fix to allow us to do exactly what I asked in the first post.
We then had an issue with an error saying Crystal Reports couldn't find the rasauditingw.dll. After a few months of going back and forth they finally looked deeper into the issue and informed me other businesses are having the same issue with the add in
they designed. They still claim it is not there software but Crystal Reports software that is the issue.
Just to clarify, the error only appeared after the add in was put in place. Anyways, after they dug some more the following post was the end game.
"The development team was finally able to get into this issue (seems other businesses are seeing this same issue now). It was in fact an issue with SAP Business Objects and where it was looking for the rasauditingw.dll.
****WARNING THIS IS DONE AT YOUR OWN RISK!!****
I AM NOT RESPONSIBLE FOR DAMAGES TO YOUR PROGRAMS OR SYSTEM THIS FIX MAY CAUSE
BACKUP YOUR SERVER OR TAKE A SNAP SHOT (VM) BEFORE ATTEMPTING ANY OF THE FOLLOWING
We copied the rasauditngw.dll file into the system32 folder and the sysWOW64 folder and then renamed the original rasauditingw.dll to rasauditingw.dll.bak (Original file in this directory: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise
XI 4.0\win32_x86).
So far so good. We have not seen any errors in the last couple of days since the fix. I hope this helps others who run into this mystery problem. Christen Steven was gracious enough to dig into this problem and quell my frustrations and issues with the
"crd.exe - Entry Point Not Found" error" "
We haven't seen any issue with our CRD server since we moved the copies of that .dll file over into our sys32 folder and sysWOW64 folder on the CRD server (our server where the Christian Steven software resides).

Migrating to Sharepoint 2013 from 2010 - Can you use the same URL for the Web Application without affecting the 2010 environment?

Hi,
I am currently trying to migrate our SharePoint 2010 environment to SharePoint 2013. The first thing I'm doing is creating a 2013 development environment to verify that this migration goes smoothly. I'm also doing this so that we will have a testing environment
after the upgrade to 2013 is complete.
So here is my question: I have a 3 tier farm including; 1 app server, 1 wfe, and 1 sql server. I have made a copy of our SharePoint 2010 database and installed that on our sql server 2012 sever (This new environment is on 3 completely separate servers from
our 2010 environment). I have also installed the prereqs and configured SharePoint 2013 on the App server and wfe servers, as well as configuring the necessary service applications (I have created a completely new 2013 database where I will migrate my 2010
database content when I'm ready).
I am now at the point where I need to create a new web application on the 2013 app server, where I will be migrating the copied 2010 database. (Also note that we have a 2010 development site called https://[email protected])
When I go to create a new web application in our 2013 dev environment, can I use the same url (https://[email protected]) to create this web app, or will this screw up our current 2010 dev environment?
I'm new to SharePoint migrations, so I apologize if this is a stupid question.
Thanks in advance for any insight you can share on this!
Boe Barlage

So, what you are recommending is that before I create a web application in my new 2013 environment, I need go into my hosts file on my 2013 app server and alter it to point to my 2013 wfe.
Then after I do that, then I can create my new web application on my 2013 app server with the same url as my 2010 testing environment
(https://[email protected]).
Then after that I should be able to access my new sharepoint 2013 environment at the same URL (https://[email protected])?
I must be missing something.
In your first reply, you told me to alter the host file on my 2010 app server and point it to my 2010
wfe (I guess I thought it probably already is). You also told me to alter the host file on my 2013 app server and point it to my 2013 wfe.
so I am confused on after I do this, what url would I access my 2010 test environment, and what url would
I access my 2013 test environment?
I am fine with having my test environment as a different URL until I am totally ready to roll everything over and kill the 2010 site. But I want to make sure that when I migrate my database, none of the site links are broken.
I also want to make sure that if I proceed this way, I want to be sure that I will be able to modify the URL to what my 2010 environment is (without a lot of headaches) when I am ready to kill the 2010 site.
Thanks again for your help, it's much appreciated!
Boe Barlage

How to connect SharePoint 2013 and Reporting Server - SQL Server 2008 - in native mode

Hi,
We are running Report Server on a SQL Server 2008 environment in NATIVE mode.
We just installed a SharePoint 2013 environment. The SharePoint roles are installed on a single server and we are using a seperated SQL Server 2012 server.
The goal: Display reports created on the Report Server in SharePoint 2013.
The problem: I cannot get the two environments connected.
I've read a dozen or more blogs but are currently more confused then before.
What are the steps I need to take to connect the two environments?
What options do I have in displaying the reports in SP2013 - do the reports need to be on the Reporting Server or can I add them to a document library... or are there other options?
Thnx!

Hi Sander,
Thanks for posting your issue, Have you activated required SharePoint 2013 features in your site collection? also, Install Report builder Model in SharePoint 2013.
Kindly browse the below mentioned URL to setup reporting Server step by step
Note: In blog, Author has taken SQL SERVER 2012, but you can try the same with SQL SERver 2008
http://blogs.technet.com/b/ldusolier/archive/2014/05/19/use-of-bi-capabilities-in-sharepoint-2013-with-sql-server-2012.aspx
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

Update Sharepoint 2013 document library folder columns using document url

Hi All,
I have a SharePoint document library. In that library I am having folder name called Folder1. In this folder Folder1 I have 4 files in it. Now. I need to update the status column of these 4 files in Folder1 folder using the url of these 4 files.
So can anyone help me in to solve this problem. I am using SharePoint 2013 and Visual studio 2012. I want the code in C#.
Thanks & Regards,
Kishore
Kishore

Hi,
According to your post, my understanding is that you want to update the field within the folder.
I have made a simple code demo below to update the field within the folder, you can have a look at it.
using (SPSite site = new SPSite("http://YourSiteURL"))
using (SPWeb web = site.OpenWeb())
SPList list = web.Lists.TryGetList("Lib1");
if (list != null)
foreach (SPListItem folderItem in list.Folders)
if (folderItem.Title == "Folder1")
SPListItem item = list.GetItemById(5);
item["Status"] = "Updated";
item.Update();
Console.WriteLine("Field update successfully...");
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

DPm 2012 r2 problem after moving Sharepoint 2013 to a differnt SQL using another alias

Similar Messages

Maybe you are looking for