C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>STSA
DM.EXE -o restore -URL http://spnt-dev-sql/sites/HNB/ -filename "C:\Backups\hnbb
ack.bak"
Another site already exists at 'http://spnt-dev-sql/sites/HNB/'. Choose a new UR
L, or specify the -overwrite flag to overwrite the existing site.
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>STSA
DM.EXE -o restore -URL http://spnt-dev-sql/sites/HNB/ -filename "C:\Backups\hnbb
ack.bak" -overwrite
<nativehr>0x80070003</nativehr><nativestack></nativestack>
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>STSA
DM.EXE -o restore -URL http://spnt-dev-sql/sites/HNB/ -filename "C:\Backups\hnbb
ack.bak" -overwrite
Wednesday, September 16, 2015
Friday, September 4, 2015
Error 1 Error occurred in deployment step 'Add Solution': A feature with ID
Error 1 Error occurred in deployment step 'Add Solution': A feature with ID 15/0e0c279a-04de-41d2-813d-6059f2ef3fdf has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
-- deletesolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o deletesolution -name HNB_Circular.wsp
-- iisreset
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>iisreset
--addsolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o addsolution -filename C:\Projects\HNB_Circular.wsp
-- deploysolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o deploysolution -name HNB_Circular.wsp -url http://spm:1111/sites/hnb -immediate -allowgacdeployment
-- deletesolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o deletesolution -name HNB_Circular.wsp
-- iisreset
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>iisreset
--addsolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o addsolution -filename C:\Projects\HNB_Circular.wsp
-- deploysolution
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>stsadm -o deploysolution -name HNB_Circular.wsp -url http://spm:1111/sites/hnb -immediate -allowgacdeployment
Tuesday, September 1, 2015
Workflow Manager Register Error , SharePoint 2013 on Windows 2012 R2
Microsoft SharePoint 2013 SP1, supports SharePoint installation on Windows 2012 R2 servers.
“SharePoint 2013 with service pack 1” and "Windows 2013 R2" can install without any errors.
when configuring Workflow Manager i had face many problem.
1. The most common error is “Register-SPWorkflowService The remote server returned an error: (404) Not Found”
To solve this issue we have to install
Service Bus Update
workflow manager cu 2
Before that ensure the workflow installation login should have the highest privilege as user()
SharePoint Designer 2013: App Management Shared Service Proxy is not installed
“SharePoint 2013 with service pack 1” and "Windows 2013 R2" can install without any errors.
when configuring Workflow Manager i had face many problem.
1. The most common error is “Register-SPWorkflowService The remote server returned an error: (404) Not Found”
To solve this issue we have to install
Service Bus Update
workflow manager cu 2
Before that ensure the workflow installation login should have the highest privilege as user()
SharePoint Designer 2013: App Management Shared Service Proxy is not installed
Standard
SharePoint
Designer 2013: App Management Shared Service Proxy is not installed
Scenario:
When compiling the workflows in SharePoint Designer 2013 and publishing the workflow I faced the following Errors were found when compiling the workflow.
When compiling the workflows in SharePoint Designer 2013 and publishing the workflow I faced the following Errors were found when compiling the workflow.
Further
details on the error revealed Microsoft.SharePoint.SPException: App Management
Shared Service Proxy is not installed.
Approach:
In
order to resolve that I did the following:
Go To
- Central
Administration > Manage Services on Server
- Check
if App Manage Service is running
- Central
Administration > Application Management > Manage Service
Application.
- Check
the App Management Service application is created, if not then create the
App Management Service application.
Ensure: When creating the
App Management Service it is important that this is enabled
Subscribe to:
Posts (Atom)