Comments for SharePoint Automation

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by Gary Lapointe

Gary Lapointe — Mon, 06 May 2013 19:51:06 +0000

There’s no URL for the farm and you don’t need to dispose the SPFarm object. If you’re on SP2010 just set the $farm variable using this: $farm = Get-SPFarm

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by Gary Lapointe

Gary Lapointe — Mon, 06 May 2013 19:49:05 +0000

You need to look at the inner exception to see what’s really going with that error. As long as you have rights to run the cmdlets (so you’re a shell admin) and you have rights to the site collection you’re inspecting, then the code should work.

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by Larry W Virden

Larry W Virden — Thu, 02 May 2013 11:41:07 +0000

I am seeing the same error. I am logged in as the farm admin. When I look at $Error, I get:
PS C:\Users\sa_spsdev\Documents\powershell> $error
Get-DocInventory : Exception has been thrown by the target of an invocation.
At C:\Users\sa_spsdev\Documents\powershell\get-docinventory.ps1:44 char:17
+ Get-DocInventory <<<< | Export-Csv -NoTypeInformation -Path d:\temp\inventor
y.csv
+ CategoryInfo : NotSpecified: (:) [Get-DocInventory], TargetInvo
cationException
+ FullyQualifiedErrorId : System.Reflection.TargetInvocationException,Get-
DocInventory

What powershell settings need to be in place for the script to work?

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by Larry W Virden

Larry W Virden — Tue, 30 Apr 2013 15:44:43 +0000

I could use some help.
I have tried to update a copy of your original script to cover several of the things you mentioned before, as well as set up the script to take the farm name as an argument. The script starts out:

function Get-DocInventory([string]$farmUrl) {
[void][System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)
$farm = New-Object Microsoft.SharePoint.SPFarm $farmUrl
:
other code from above
:
$farm.Dispose()
}

Get-DocInventory http://mysite | Export-Csv -NoTypeInformation -Path d:\temp\inventory.csv

When I run my this script file, I get this as my output:
New-Object : Cannot find type [Microsoft.SharePoint.SPFarm]: make sure the asse
mbly containing this type is loaded.
At C:\Users\spsadmin2\Documents\PowerShell\Get-DocInventory.ps1:8 char:23
+ $farm = New-Object <<<< Microsoft.SharePoint.SPFarm $farmUrl
+ CategoryInfo : InvalidType: (:) [New-Object], PSArgumentExcepti
on
+ FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewOb
jectCommand

You cannot call a method on a null-valued expression.
At C:\Users\spsadmin2\Documents\PowerShell\Get-DocInventory.ps1:55 char:16
+ $farm.Dispose <<<< ()
+ CategoryInfo : InvalidOperation: (Dispose:String) [], RuntimeEx
ception
+ FullyQualifiedErrorId : InvokeMethodOnNull

I know the second error is because of the first. I just don't know why the assembly is not being loaded.
This is SP 2010 SP 1, powershell v2.0. I am on as a farm admin, and opened the sp 2010 management shell as an admin.

Is there anything I can check to see what is going wrong?

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by Gary Lapointe

Gary Lapointe — Fri, 19 Apr 2013 01:53:32 +0000

Yup. Just change the if statement to this: if ($list.BaseType -ne “DocumentLibrary” -and $list.ItemCount -lt 5000) {

Comment on Getting an Inventory of All SharePoint Documents Using Windows PowerShell by JJ Blackshear

JJ Blackshear — Fri, 19 Apr 2013 01:41:37 +0000

Hi Gary. Thank you for your efforts. Is there a way to modify this so I can identify lists and libraries with >5,000 items?

Thanks!

Comment on Updating SharePoint 2010 User Information by Gary Lapointe

Gary Lapointe — Fri, 12 Apr 2013 16:10:21 +0000

Any permissions or alerts assigned to the user will be lost. Might be some other implications but I can’t remember any others at the moment.

Comment on Deploying SharePoint 2010 Solution Package Using PowerShell (Revisited) by Gary Lapointe

Gary Lapointe — Fri, 12 Apr 2013 16:08:29 +0000

Make sure you don’t have any attributes or comments or anything else for the WebApplication element. It should look just like the example in the help. If you add a comment or an attribute then PowerShell will treat it like an XmlElement and not a string which is what is needed. If you need the additional information in the XML then you’ll need to change the code so that it extracts the value out rather relying on PowerShell’s automatic type conversion.

Comment on Fix: The trust relationship between this workstation and the primary domain failed by Gary Lapointe

Gary Lapointe — Fri, 12 Apr 2013 15:57:51 +0000

Cool! I never knew about this one. Thanks for sharing!!!

Comment on Fix: The trust relationship between this workstation and the primary domain failed by Alexey Krasheninnikov

Alexey Krasheninnikov — Fri, 12 Apr 2013 14:25:05 +0000

How about PowerShell?
PS:> Test-ComputerSecureChannel -Repair