Hot answers tagged

6

Are you running Server 2008? If so, you need to open the command prompt using the "Run as Administrator" option.


6

You can use the following stsadm commands to get the information you need: stsadm -o enumzoneurls stsadm -o enumalternatedomains or use the PowerShell cmdlet: Get-SPWebApplication


6

I recently ran into the exact same issue in SP 2013 where my Dev machine had the RTM install and the target server the June CU. We ended up copying the Content Database from SQL directly, reattaching and associating it to a Web Application and it worked flawlessly. It seems the Restore command is no longer backwards compatible and can't be relied to restore ...


5

I'm pretty sure that if your assemblies contain feature receivers then they need to be installed into the GAC. There is a post about it here, but in my opinion it doesn't give a good explanation why. My theory is that when you attach a feature receiver to a feature, the assembly needs to be globally available, since FeatureInstalled/Activated etc can be ...


5

Check if your Windows SharePoint Services Administration and Windows SharePoint Services Timer jobs are running. Also after ensuring, run this command stsadm -o execadmsvcjobs


5

PowerShell is Microsoft’s next-generation scripting language offering direct access to .NET objects, complex flow and structure capabilities, and an object pipeline that makes passing objects from one command to another extremely easy. Using Powershell in SharePoint 2010, Almost every aspect can be manipulated using any of the more than 500 out-of-the-box ...


4

I've been successful with the following script Process exportSite = new Process(); string commonFilesPath = System.Environment.GetFolderPath(System.Environment.SpecialFolder.CommonProgramFiles); string commandLine = " -o export -url " + SPContext.Current.Web.Url + " -filename c:\\" + tempName + ".exp -overwrite -includeusersecurity"; ...


4

'A failure occurred during the processing of this command. Check diagnostic logs for more information' is in fact "Access Denied error to the User Profile Service Application". TO resolve this issue, Navigate to Manage Service Applications ---> User Profile Service Application Name ----> select Permissions from the ribbon ----> Add your user ...


4

Not sure but you could always just pop open a command line "As Administrator" - you only get the UAC pop up once that way.


4

you can use stsadm -o enumsolutions Be aware that its a best practice to always deploy from the same WFE. That way you wont have conflicts between hanging jobs. The problem is related to the fact that stsadm -o execadmsvcjobs only runs pending jobs on the WFE you are on, not on the entire farm. Gary Lapointe created a job that will run jobs on all ...


4

Checking the list of ststadm operations seems that there is no stsadm command for disabling a timer job. There is only a command to delete a timer job (deletessptimerjob). In that case you are left with two options: Disable the timer job using the UI in Central Administration (Central Administration -> Operations -> Job Definitions) Disable the timer job ...


4

My guess would be that SharePoint caches the contents of the template store and an IIS reset is required to rebuild that cache to pick up the new template that you just added.


4

Please follow steps given below to ensure SharePoint Administration Services is available: Click on Start->Run->Services.msc. Search for "SharePoint 2010 Administration" service and make sure Status is Started. If it is not enabled, start the service and re-execute the command.


3

Yes, it's cache related. When you execute "addtemplate" from stsadm, the template file is actually saved to the content database. To be specific, it will be added as a custom global web template " SPPersistedCustomWebTemplate" through the SharePoint "SPWebService" object (which is a sort of helper object that helps SharePoint Web Application retrieve and ...


3

First, get all your web applications and iterate through them. While in the loop print web application name and application pool name. Last, iterate all solutions and print their names - like this: $contentWebAppServices = (Get-SPFarm).services | ? {$_.typename -eq "Microsoft SharePoint Foundation Web Application"} foreach($webApp in ...


3

A couple of things here: Using backup/restore to move a site between environments is only supported under specific circumstances. For publishing sites, you need SP2 and the April 2009 Cumulative Update or later (not sure without checking version numbers if you have this). Stefan discusses this for publishing sites here, but I'm not sure how this applies to ...


3

In your example you are backing up the root site collection of machine1 and restoring it under a managed path on machine2. You may want to make those consistent. Emad is correct about step #2, as long as the application is setup on the server you will not need to create a content db. One last tip, make sure that you have any customizations or solutions ...


3

the problem is that you cannot use RWEP to create the site collection. RWEP takes the the identity of the app pool and most likely (if you configured your farm correct) this account is not member of the farm adminstrators group - which is required to create the site collection. If you run the code in central admin it will work though, since it takes the ...


3

PowerShell is the replacement for stsadm. If you need to use stsadm, which is located at c:\program files\commonfiles\microsoft shared\web server extension\12\BIN, use a standard cmd window not PowerShell to execture your commands.


3

http://lmgtfy.com/?q=stsadm


3

You dont mention the version of SharePoint you are using, but since you mention stsadm i am gonna assume you are using SP2007. You should follow this guide on technet. Be aware that the procedure varies depending on if you are running named instances (alias) or not. For SP2010 use this article instead.


3

stsadm -o execadmsvcjobs does not always wait until the job you created has finished processing, nor does it ensure that the job processed successfully. A safer approach is to watch the solution deployment status in Central Administration and not execute your ActivateFeature command until you see that it has deployed. I have also seen it happen where the ...


3

In general, I've found two superior alternatives to launching stsadm as a separate process. First is using the SharePoint Object Model. In your case, this would be with the function SPAlertTemplateCollection.InitAlertTemplatesFromFile. This gets you the best error handling story. If there's something that's not exposed via the OM or it's more work than ...


3

Your scope for feature is at "Web Application" level feature and therefore be visible at Central Administration -> Application Management -> Manage Web Application Features See technet Edited You can activate Web Application Feature by giving it's url. stsadm -o activatefeature -id GUIDID -url https://abc303.development.com/ If you're facing ...


2

You are missing the ElementFile element. From what you've described, your feature.xml should look something like this: <?xml version="1.0" encoding="utf-8"?> <Feature Title="YourFeature" Description="YourFeature" Id="GUID" Scope="Site" Version="1.0.0.0" Hidden="FALSE" DefaultResourceFile="core" ...


2

You need to bring your new SharePoint environment up to at least the same patch level as the one that failed. An easy solution would be to apply the latest Service Pack and possibly the latest Cumulative Update to the new farm. Once that is done, you should be able to attach the old content database and it should upgrade as part of the attach.


2

I found the answer. The reason is because the version numbers for my FARM 1 SQL DB is different from the one on FARM 2. I upgraded both servers to the same built number and everything worked fine. Thanks to everyone that replied.



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