Scribbled during the madness

SharePoint | Extracting solution files

On September 7, 2011, in SharePoint, by Andy

The other week I was in the process of migrating a SharePoint farm from one farm to a new farm. However, I found that there were a number of undocumented solutions installed that I needed to move as well… The WSP’s had been misplaced. We knew we could do this in code. But figured PowerShell would be a better idea. Here is that code:

[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)`

| Out-Null

[Microsoft.SharePoint.Administration.SPFarm]$farm`

= [Microsoft.SharePoint.Administration.SPFarm]::Local

[Microsoft.SharePoint.Administration.SPSolutionCollection] $solutions`

= $farm.Solutions

[string] $path = Get-Location

foreach($solution in $solutions)

{

Write-Host “Solution Name: $($solution.Name)”

$solution.SolutionFile.SaveAs((Join-Path $path $solution.Name));

}

Visio | Internal error: #3400

On September 7, 2011, in SharePoint, by Andy

When trying to save to a visio document to document library you receive a “Visio internal error: #3400 – Action 1787: Check in File” message.

This seems to be caused by content types that use managed metadata. You should still be able to save the file. But you will not be able to check it in.

Workaround

Save the file and check in via the browser. Once you have populated the metadata in the browser, any further changes/checkin’s via Visio should still work.

Nintex | Failed to Activate “Nintex Reporting 2008 Team Site Reporting”

On September 7, 2011, in SharePoint, by Andy

I came across an issue when installing and trying to activate Nintex Reporting 2008 Workgroup Edition version 1.3.0.5 to a SharePoint Site.

Upon activating the “Nintex Reporting 2008 Team Site Reporting” feature, I received the error “A Web Part or Web Form Control on this Page cannot be displayed or imported. The type is not registered as safe.” http://connect.nintex.com/forums/thread/14467.aspx.

After checking my application pool account was a member of the nintex reporting role, I checked the safe controls section of each zone for the web application and found that they were indeed missing entries, however, the entries described on the forum as incorrect. These should be:

……..And must exist in the web.config files of each site for each zone of the web application.

SharePoint | “cmdlet not recognized”

On September 7, 2011, in SharePoint, by Andy

So, I’ve had a rough week. Automating a whole bunch of stuff for several client deployments.

Back Story

This function library I have been working started it’s testing phase on Friday… The functions had been created post farm provisioning and all worked sweet. So we decided to do the full monty and build the farm completely (post-binary install). So we kicked off the script (on a single server farm) and waited, everything ran (including Enterprise search) up until Excel services went to install. Bam, lots of red and the error message the boiled down to

cmdlet ‘Get-SPExcelServiceApplication’ not recognized

So, we’re baffled. We knew this had previously worked. Why not now? To confirm this, we execute the function on it’s own in a separate PowerShell instance. Boom it worked… Ok, so it does work I thought.. We rolled back our VM and tried it again, however this time I commented out the function executing before the excel function. Ran the script, again same error “cmdlet ‘Get-SPExcelServiceApplication’ not recognized”… A little frustrated I commented out the excel function, rolled back the VM and started again, again.. This time we got past the function with no problem, managed to install Word Automation Services, Performance Point Service, and just when I thought we were out of the woods; “cmdlet ‘Get-SPVisioServiceApplication’ not recognized”.. AHHHHhGHHG. Running the function in a separate window proved that it worked fine. So, after storming around having a couple drinks and taking some time out, I embarked on the mission of stepping through the script. Long story short, I got the Excel services and everything worked sweet. I then ran Get-Help Get-SPExcelServiceApplication in the PowerShell console of PowerGUI script editor and funnily enough, the command was not recognized. I opened a PowerShell instance, loaded the cmdlets and executed the same command, and funnily enough it found it. “A-HA”, I exclaimed. I know what it is. I went back and edited my Farm Provisioning function to re-add the PowerShell cmdlets, rolled back the VM, uncommented anything and ran the script. BOOOOM, it worked. Issue It seems that something like 95% of cmdlets seem to be available and recognized pre-farm creation. However, if you do not re-load your cmdlets after farm creation not all cmdlets are recognized. So far I have found this to be an issue with:

Excel Services
Visio Services

Resolution

After you create/join your farm. Reload your SharePoint cmdlets. This will save you lots of time/pain/heartache … So if you’ve previously loaded your cmdlets the following code should be sufficient (add this to your own function or whatever):

Remove-PSSnapinMicrosoft.SharePoint.PowerShell`
-ErrorAction SilentlyContinue

Add-PSSnapin Microsoft.SharePoint.PowerShell`
-ErrorAction SilentlyContinue

Hello World

On September 7, 2011, in Uncategorized, by Andy

So…. my old blog got hacked or spam attacked… And after fighting to save it, I gave up and deleted it… So now, I introduce, Andy’s Blog 2.0… I’ve saved my blog posts and will update them as soon as I can…

Scribbled during the madness

SharePoint | Extracting solution files

Visio | Internal error: #3400

Workaround

Nintex | Failed to Activate “Nintex Reporting 2008 Team Site Reporting”

SharePoint | “cmdlet not recognized”

Back Story

Resolution

Hello World

Lately

Snippets From Me