How to find the currently running SharePoint 2007 Timer jobs using STSADM?
Not sure if you can do that with default
stsadm commands, but possible if you write a
custom stsadm command.
Someone already wrote a stsadm command where
you can enumerate job definitions
with stsadm. Just download and
install.
There is also SharePoint
Manager available which shows
that information and many other. It
is a very good tool that I can
recommend for SharePoint developers
and Administrators.
Related
Using CAML or some other query system, how can I find items that use custom code and organize by modified date?
And the background. My group is looking to upgrade a 2007 SharePoint installation to SPO. The problem we're having is a lack of clarity as to what on the site is junk and what is a custom code set. The first idea was just to run through manually and make note of every node. As there are 5,200 nodes, this is pure insanity. I've done some research to find that CAML is how to query a particular site in SharePoint, however I cannot seem to figure out how to query everything at the same time.
I tried to make a view in the root, but again, it only queries the particular level you're on. I'm having the feeling that I might need to write a tool for this and spider the site, but am unsure where to begin. After trying a couple of tools (Stramit Caml running in visual studio and SPUD) I seem to be running in place as I don't understand how the connection works.
Any advice or stories like this?
To scan your environment and detect where custom solutions are used, your best bet is to use the stsadm command called preupgradecheck. This is executed from the commandline on one of your web front end servers, invoking stsadm.exe.
From Microsoft:
The Stsadm command provides a rule-based scanning operation to determine whether servers in an existing SharePoint environment meet the core requirements for upgrading from Windows SharePoint Services 3.0 and related products to future releases of SharePoint Products and Technologies.
The pre-upgrade scanning and reporting operation is implemented as Stsadm –o preupgradecheck, and can be run with or without parameters.
Upon execution, the command checks your environment against various rules. The result of each rule check is written to both an XML log file and a text log file, located in the the %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS directory, and when the command finishes it will display an HTML file in the default web browser summarizing the results.
I'm trying to make a SharePoint workflow start automatically for any new document that is uploaded to a specific doc library. I've configured the workflow in SharePoint Designer to auto start for new documents or changed documents. However, the workflow never starts automatically! I can run it manually, but it won't execute itself.
I've searched around and have found the core issue, which is reflected in my log:
"Declarative workflows cannot automatically start if the triggering action was performed by System Account. Canceling workflow auto-start."
However, all the fixes I've seen have not worked for me. A common solution is to not run or create the workflow as the SharePoint System Account. Well, my SharePoint service accounts are not the ones I'm logging in as to upload my documents nor was it the one I used to create the workflow. I've tried editing & re-publishing my workflow as a totally new account and it still won't auto-start.
Just focus on two things:
Workflow will never start automatically with system account.
Check the options Start workflow automatically when an item is created or changed from Workflow Start Options.
While publishing the workflow, u need to select the checkbox Start workflow automatically when an item is created or changed for the workflow to start automatically or else whatsoever the WF will not start automatically.
Instead of using Sharepoint system user account, u could use an account having contribute permission on site level and full control over the library
Run the command at the server in powershell
stsadm.exe –o setproperty –propertyname declarativeworkflowautostartonemailenabled –propertyvalue yes
After I did that, the workflow runs perfectly although it shows the created by as being "system account".
Hi
I know I can use power shell or central admin to backup SharePoint site collection or Site,is there a way to automate this process or I have to create a scheduled task that runs either power-shell or stsadm command?
normally what we use to do is create a batch file of stsadm commands for backup and associate it with windows scheduler job. and i think thats the best approach you can do the same for powershell scripts as well
You can automate the backing of sharepoint site collection using SPTimer Job.
Based on the schedule SPTimer will back your site collection/site periodically.
Since SPTimer job is integrated with SharePoint this can be implemented easily.
Take a look at this. It's descriptive.
http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2010/12/21/sharepoint-2010-cookbook-powershell-script-to-backup-a-site-collection-automatically.aspx
We want to activate the existing future for more than 100+ site-collections, what would be the right choice? can we achieve this through Powershell?
If you don't want to code yourself, you can always download the SharePoint Feature Admin Tool from Codeplex.com.
It will allow you to select a Web Feature and activate/deactivate in recursively on a Site Collection.
Yes powershell would make this easy.
But there is also the stsadm command "activatefeature".
Together with the stsadm command "enumsites" and a bit of creating command script building you should go a long way.
One of our product will consist of multiple SharePoint solutions. Now we're wondering what would be the best way to provide an easy deployment to our customers? At the moment we deploy each solution by hand, which is OK during development process but not acceptable for our customers.
For your information, we're using VSeWSS 1.3 for development and solution packaging.
So how do you offer your solutions to your customers? Do you write installation scripts using STSADM commands? What other options do we have?
WSPBuilder
Personally I use WSPBuilder for packaging and find it much easier to work with than VSeWSS. However if VSeWSS is working for you then that's great.
One of many the benefits I found of using WSPBuilder is that it's easy to integrate into a build system. It's just a simple, but clever, commandline tool.
Batch File
For deploying multiple SharePoint solutions to our customers I usually provide a batch file that contains the necessary STSADM command and prompts them to enter any environment specific data i.e. site collection urls etc...
SharePoint Solution Installer
There is also a nice GUI installer,called SharePoint Solution Installer, that you can use in-conjunction with SharePoint solution files. Check it out it might suit your needs.
alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=sharepointinstaller&DownloadId=18625
SAF - SharePoint Action Framework
It's worth pointing out SAF; which is an extremely comprehensive framework that can automate installation and configuration tasks, using either MSBuild, Powershell, Stsadm or a custom SharePoint feature.
We just use plain old batch/cmd files. If you need to "productize" this, just wrap up all solutions in a selfextracting rar package and have it run the batch file after unpacking.
Stick to Microsoft products. Powerbuilder is being groomed to gradually take over from STSADM for this type of task. In a farm scenario (remember, yours may have to grow over time), this would be the tool to use to push out solutions to all front-end Web servers.
EDIT:
MS are preparing a final version of VSE 1.3 to ease the migration of 2007 solutions to the 2010 environment.
Have you looked at Microsoft SharePoint Designer?
not sure if it will do all you need, but it does allow you to package sites or individual objects that you can then run on another SharePoint install.