Archive
#SharePoint 2010 Missing Server side dependencies Central Admin Help site orphaned #SP2010 #PS2010 #PowerShell
   I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
Whilst working on a client site today to deploy the June 2012 CU to their SharePoint / Project Server 2010 farm I came across an issue in the pre-update health check. The issue was identified by the SharePoint health analyser as Missing server side dependencies. This particular missing dependency was an orphaned site in the Central Administration content database. The Help site was present in the central admin content database but not in the farm configuration. The exact error for search engines is below:
[SiteOrphan] Database [EPM2010_AdminContentDB] contains a site (Id = [d2df5cfd-26fc-419f-bd23-07b61d805bbd], Url = [/sites/Help]) that is not found in the site map. Consider detach and reattach the database. The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary.
The reason why this site was not created successfully or potentially orphaned after the install is unknown.
Anyway enough about the error, what about the fix? As the explanation suggestions the first option I tried was to detach and reattach the content database. I was a bit caution of doing this as it was the farm central admin content database, so I tested this on my own farm first.
Running the Dismount-SPContentdatabase command failed with the error below, probably because this content database is attached to an SPAdministrationWebApplication web application rather than a normal SPWebApplication.
Next I tried combining the Get-SPContentDatabase command and piping this to the Dismount command and that worked successfully. The example command is below:
get-spcontentdatabase -webapplication http://vm353:15000 | dismount-SPcontentdatabase
Then I ran the normal Mount-SPContentDatabase command to attach the same content database that was detached above:
Mount-SPContentdatabase -name EPM2010_AdminContentDB -DatabaseServer vm353 -Webapplication http://vm353:15000
The Central admin site opened (good start 
), I then accessed the http://vm353:15000/sites/help site which prompted me to set the template. After setting the template for the site I was able to access the site without any issues. When the farm was installed I think part of the help site provisioning failed to set the site template for some unknown reason which caused the site creation to be incomplete. I then reanalysed the missing server side dependencies error and the issue was resolved, the June 2012 CU also deployed successfully.
I would strongly recommend having full SQL database backups of all farm databases and SharePoint server snapshots / images before attempting this fix.
Hopefully this will help out anyone else who comes across this error.
Practice makes Perfect Part 3 – Views
This post in the Practice makes Perfect series is about views. The reason behind it is that I myself when starting to use Project for my Project plans always used the default view of Project to edit and view my Project Plan. I sometimes switched to the Tracking Gantt or resource sheet but that is about it.
Great view isn’t it!
Only when I became a Project Consultant and had to know a lot more of Project that I realized I was missing out on something really easy but with so many benefits.
For this post I am again using the Project Professional 2013 preview version. This is not the finally product so things might change.
Default view
While the default view of Project Professional gives you access to create a project plan quickly it lacks in certain areas when it comes to update your plan or being more specific to the data you need/want to see.
To change this you can do two things:
- Add/remove new columns.
- Or make a new view.
Why would I make a new view if I just can add/remove columns?
This is a good question. Add/removing a column might be easy but it can also create a lot of columns you don’t actually need all the time. Working with views gives you the ability to quickly switch between data you want to view. Instead of adding and removing columns every time.
So what kind of views can a make?
For instance like shown in this post you can make a view what make it easy for every Project Manager to update their plan with % Complete, Work, Remaining Work. Other example might be a view with your RAG (Red, Amber and Green) indicators (RAG indicators will be covered in a different post), Resource information displaying names, work and actual work. I could go on but it all depends on what you as Project Manager want to see. As shown in this post making a view depending on the depth will only take you between 5 > 30 minutes.
So how do I make a view?
The first thing you need to know that a view is built up from 3 components. Were two are optional (Filter and a Group) and one is not (Table).
We are going to start making this view by making a table. In Project Professional go to View > Tables and select More Tables in the dropdown menu.
Here you can choose to create a new table.
For the purpose of this post I am going to create a view that makes it easy to update the status of a project.
In the image below I made a table with fields like % Complete, Remaining Work, Work and Start and Finish as an example.
You properly will be playing around with the alignment of the data and the width of the columns but when you are done you can press ok and you are done.
Now the next thing we can do is define a filter or group this is optional and this post I am not going to make use of them (Filters and groups will be discussed in a new post).
Now that I have my table I want to start using it in my own view. In Project Professional go to View > Other Views highlighted in the picture below.
Select New to create your view.
Give your new view a name and a screen you want to use. There are a lot of options here and I would go through them all to see what you find useful. If I only want to see data a good screen to take is the Task Sheet. This will leave out the Gantt Chart and basically only show you the columns.
To make a view you are required to always choose a filter or a group. If you do not want a filter or a group you will need to select No Group for the Group and All Tasks for the filter. These are the default options if you don’t want a group or filter interfering with your view. When done you can see your new view in the views bar. The images below are the results.
This view is created in about 5 – 10 minutes. Some more complicated views might take longer but this gives you a fast way to make a view, to view the data you want. In this instance updating % Complete and Remaining Work.
As always you have to experiment with making views but I can promise you that it is definitely worth it. This creates standardization on how you view your data in your project plan. Views themselves can even be used as a report for your management. The great thing about views is that once you make them you can use them for every project.
Making views makes your life as a Project Manager much much much easier. Don’t take my word for it start playing around with it yourself.
via SpeakingSilent » Robin Kruithof http://speakingsilent.wordpress.com/2012/08/09/practice-makes-perfect-part-3-views/
 I am Robin Kruithof. I am working at CXS in the Netherlands as a Microsoft Project Consultant. My passion lies in Project Management and everything in the Project Management domain.
This article has been cross posted from speakingsilent.wordpress.com/ (original article) |
Generate unique X and Y coordinates or grid references from a row number
I was creating an SSRS report and using a matrix table. I needed to be able to position data within each group by. To do this i needed create a X and Y number for each item where the 2 together would be unique.
This is an example of what i wanted
|
Row number |
x |
y |
|
1 |
0 |
1 |
|
2 |
0 |
2 |
|
3 |
0 |
3 |
|
4 |
1 |
1 |
|
5 |
1 |
2 |
|
6 |
1 |
3 |
|
7 |
2 |
1 |
|
8 |
2 |
2 |
|
9 |
2 |
3 |
And here is the SQL that creates it
SELECT ROW_NUMBER() over (ORDER BY prj.ProjectName) as Row
, ((ROW_NUMBER() over (ORDER BY prj.ProjectName)) - 1) / 3 as X
, ((ROW_NUMBER() over (ORDER BY prj.ProjectName)) - 1) % 3 as Y
This took a lot longer to work out that i care to admit. So hopefully someone else will find this useful
If you need more columns before the split then simply change the 3 to be what ever number you need.
via Buzz Blog http://paulbuzzblog.wordpress.com/2012/08/09/generate-unique-x-and-y-coordinates-or-grid-references-from-a-row-number/
 Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
New Programming Jargon
Love this new list of jargon used by teams around the world. Find it here http://www.codinghorror.com/blog/2012/07/new-programming-jargon.html
My favourite – possible because it happens far to often
Protoduction
A prototype that ends up in production. Heard this from a tech at the Fermi lab. He said he didn’t coin the term but had heard it used a number of times at Fermi.
via Buzz Blog http://paulbuzzblog.wordpress.com/2012/08/06/new-programming-jargon/
|
Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
Practice makes Perfect Part 2 – Baselines
When I was in a Prince2 Practitioner refresh course the other week I asked around who uses Project Professional to plan their projects. Only a few did, then I asked who uses baselines in their plans. None of them responded. This gave me the incentive to make a post about baseline usage in Project Professional.
For this post I will again use Project Professional 2013. As always this is not the finished product and images do not represent the final version. Things might change.
What is a baseline?
A baseline within project is basically a snapshot of your plan. Almost like taking a photo. This is very handy as every Project Manager knows a project plan is subject to a lot of changes. Using baselines give you a good opportunity to track what has changed in your plan.
The first thing you need to determine is “when am I making my first baseline”. In large organizations this is mostly handled by a PMO (Project Management Office) or by the Project Manager. In small organizations the Project Manager is generally responsible for setting the first baseline. If we take PRINCE2 for example your first baseline could be set at the end of the process Initiating a Project.
It is also relevant to know that Project Professional gives you 11 baselines per project. Baseline (0) to Baseline 10. When you have determined when your first baseline has to be set you have to decide which baseline to set. I recommend to always use Baseline 10. The reason behind this is that baseline (0) is easier to override by accident than baseline 10 is.
Where can I set the baseline for a project?
In Project Professional you can set the baseline under Project > Set Baseline Schedule.
As you can see in the image below you got a few options. You can select which baseline to set, Set interim plan. Set a baseline for Entire Project or Selected tasks. For this exercise I will set my first baseline for the Entire Project.
When you go back to the same screen you can see on which date you last saved your baseline. So what can you do with that? You can make it visible in your project plan. Go to Format > Baseline and select the baseline you have set. In my case this is Baseline 10. A other option is to set your Gantt view to Tracking Gantt.
When you selected this option or a tracking Gantt a bar is added in your Gantt Chart which represents the baseline. In the image below it is the grey bar.
During a project you are able to make multiple baselines to track where you are delayed or even ahead of schedule and why. I recommend you make a new baseline when you start the next phase of your project. By doing so you can so by the end of the Project where delays have occurred. These delays can then be added to your lessons learned report.
After making baseline 10 I made some modifications to the plan by increasing duration of some tasks. I also added the baseline10 Duration column to my screen to show you what I actually had planned and where the delays have occurred.
As you can see by the grey bars in my chart my project has a significant delay. This also gives you a good overview where the delays occurred. Pretty useful when reporting to the Project Board.
Reporting of baseline data within Project Professional 2013
In the image below I made a report displaying the scheduled duration vs. duration of baseline 9 and 10. This report is made by the new functionality of Project Professional 2013. (Yeah I know this is really cool!)
Being able to see where your project plan is delayed or ahead of schedule can help any Project Manager. In the case of a delay he/she can take corrective measures. For example the Project Manager could request an extra resource for a specific task to make it finish earlier and by doing so getting back on track.
The usage of baselines in a Microsoft Project plan is one of the most useful tools you can have during a project. It can really help you out. As always experiment with baselines in Project and see for yourself. I hope this gave a little insight in the use of baselines.
via SpeakingSilent » Robin Kruithof http://speakingsilent.wordpress.com/2012/08/06/practice-makes-perfect-part-2-baselines/
|
I am Robin Kruithof. I am working at CXS in the Netherlands as a Microsoft Project Consultant. My passion lies in Project Management and everything in the Project Management domain.
This article has been cross posted from speakingsilent.wordpress.com/ (original article) |
Infopath “The following form template cannot be upgraded because it is not currently uploaded on this farm” #sp2010
So what i was trying to do is upload a new form template to a clients QA system. Something that has been done tens of time since the system went live. But today I get.
Now i have never seen this message before so i instantly start googling to try and save the day.
I have to say not a lot of stuff around this error is available but there are a couple of MSDN forum posts that got me in the right direction.
The SharePoint farm in question has recently had some more servers added to the farm and what i suspect has happened is that the form files have not correctly deployed to the new servers. But to prove this i need the feature GUID that is created when you first upload a InfoPath form.
I found the quickest way to get this is to navigate to the site collection the form exists on. Go to Site settings and under Site collection Administrators select the Site Collection Features in the list you will see a feature that maps to the name of the XSN file.
Click on the Deactivate button (don’t worry there is a confirmation step). Now in the query string the feature GUID is shown. Copy this as you will need it later. You don’t need to deactivate the solution so can close the page if you wish.
I was then able to see, under Solution Management within central admin the WSP called the same GUID. Clicking on the WSP showed me that the wsp had not been deployed to all the servers in the farm. For some reason all of the other WSP in the list had all been deployed. I guess i was just lucky that this was the only one.
Now to fix the issue you need to run an STSADM command
stsadm -o uninstallfeature –id <the feature GUID you got from the query string> –force
This will remove the feature and i guess some other magic that fixes stuff.
Now the form can be upgraded without an error. Once the form has upgraded the feature is reactivated automatically (did for me anyway)
And YAY it all works again. 5 minutes job only took an hour
Hope this helps someone
|
Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
Getting Project Server database information via C# / How to run PowerShell command in C#
For a long time now I have had a few scenario’s where it would be helpful for me to know what the database server and database names are of a Project Server instance. The PSI does not provide this information but there is a PowerShell command that will give you the information.
Get-SPProjectWebInstance –url <URL>
This gives me all the info a want about the instance.
So now I know I can get the info i need i just need a way of getting this within c# code.
Helpfully you can use System.Automation to execute PowerShell scripts within .NET
We start with a simple method that will execute PowerShell commands
private string RunScript(string scriptText)
{
string addWss = "Add-PSSnapin microsoft.sharepoint.powershell";
Runspace runspace = RunspaceFactory.CreateRunspace();
runspace.Open();
Pipeline pipeline = runspace.CreatePipeline();
pipeline.Commands.AddScript(addWss);
pipeline.Commands.AddScript(scriptText);
pipeline.Commands.Add("Out-String");
var results = pipeline.Invoke();
runspace.Close();
StringBuilder stringBuilder = new StringBuilder();
foreach (PSObject obj in results)
{
stringBuilder.AppendLine(obj.ToString());
}
return stringBuilder.ToString();
}
The above code needs
using System.Management.Automation; using System.Management.Automation.Runspaces;
NOTE: You’ll need to add a reference to the version of PowerShell you have installed in your GAC to the Visual Studio project file. To do so, you’ll open the project file as a text file and add the following line into the <ItemGroup> section:
<Reference Include=”System.Management.Automation” />
I was able to cheat and “browse” to the assembly using the following path
C:\Windows\assembly\GAC_MSIL\System.Management.Automation\1.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Now that we have the helper method I can actually get the info I want.
string answer = RunScript("Get-SPProjectWebInstance -url http://vm641/pwa2");
string reportingDatabaseServer = string.Empty;
string reportingDatabaseName = string.Empty;
var output = answer.Split(new string[] {Environment.NewLine}, StringSplitOptions.RemoveEmptyEntries).Cast<string>();
reportingDatabaseServer = (from x in output where x.StartsWith("ReportingServer") select x).First().ToString();
reportingDatabaseName = (from x in output where x.StartsWith("ReportingDatabase") select x).First().ToString();
reportingDatabaseServer = reportingDatabaseServer.Replace("ReportingServer", "").Replace(":", "").Trim();
reportingDatabaseName = reportingDatabaseName.Replace("ReportingDatabase", "").Replace(":", "").Trim();
Bingo I have the name of the reporting server and the database name.
I needed this months ago to auto configure a PSI extension that was written but i need it now to auto configure a feature when it is deployed.
I’ll wrap all the above code into a single class that accepts the instance URL in its constructor and then expose properties with the information.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Management.Automation.Runspaces;
using System.Management.Automation;
using System.Text;
public class ProjectWebInstanceInformation
{
#region Fields and Properties
public string ReportingServer { get; private set; }
public string ReportingDatabase { get; private set; }
#endregion
#region Constructor
protected ProjectWebInstanceInformation()
{
}
public ProjectWebInstanceInformation(string Url)
{
try
{
string answer = RunScript(string.Format("Get-SPProjectWebInstance -url {0}", Url));
string reportingDatabaseServer = string.Empty;
string reportingDatabaseName = string.Empty;
var output = answer.Split(new string[] { Environment.NewLine }, StringSplitOptions.RemoveEmptyEntries).Cast<string>();
ReportingServer = (from x in output where x.StartsWith("ReportingServer") select x).First().ToString().Replace("ReportingServer", "").Replace(":", "").Trim();
ReportingDatabase = (from x in output where x.StartsWith("ReportingDatabase") select x).First().ToString().Replace("ReportingDatabase", "").Replace(":", "").Trim();
}
catch { }
}
#endregion
#region Methods
private string RunScript(string scriptText)
{
string addWss = "Add-PSSnapin microsoft.sharepoint.powershell";
Runspace runspace = RunspaceFactory.CreateRunspace();
runspace.Open();
Pipeline pipeline = runspace.CreatePipeline();
pipeline.Commands.AddScript(addWss);
pipeline.Commands.AddScript(scriptText);
pipeline.Commands.Add("Out-String");
var results = pipeline.Invoke();
runspace.Close();
StringBuilder stringBuilder = new StringBuilder();
foreach (PSObject obj in results)
{
stringBuilder.AppendLine(obj.ToString());
}
return stringBuilder.ToString();
}
#endregion
}
|
Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
Extract logs from #SharePoint ULS logs #ProjectServer #PS2013 #SP2013
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
This post follows on from my previous post regarding the new log level manager functionality in Project Server 2013: http://pwmather.wordpress.com/2012/07/26/projectserver-ps2013-log-level-manager-sp2013-sharepoint-msproject-powershell/
Once configured, all activity on the farm for that particular entity, depending on the logging level set, is logged in the SharePoint ULS logs.
As mentioned in my last post, I said that I would create a simple PowerShell script that will extract the Project Server 2013 log level manager logs into a custom file to make it easier for viewing.
The script is available from the Microsoft Script Center below:
http://gallery.technet.microsoft.com/scriptcenter/Extract-logs-from-09b0e7bb
The script can be seen below with comments for configuration options:
# set the required date, below will set today, other days / dates can be
# used. For example, to get yesterdays logs use
# $Date = get-date -format "yyyyMMdd" (get-date).AddDays(-1)
$Date = get-date -format "yyyyMMdd"
# if you want logs from a specified date, remove the $Date variable from the where object
# and specify the string, for example for 27/07/2012 use:
# where-object {$_ -like "*20120727*"}
$files = Get-ChildItem "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS" | where-object {$_ -like "*$Date*"}
foreach ($file in $files)
{
# this script will copy any row that contains LogLevelManager!, to copy other
# logs, update the string in the where object, for example you could use the entity UID
get-content -path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\$file" | where-object { $_ -match ‘LogLevelManager!’} | Out-File C:\PSLog$Date.txt -append
}
Running the script:
Creates a new text file in the specified location, in this example, the root of the C drive:
Whilst this script is aimed at extracting the Project Server log level manager logs, it could also be used to extract logs for other SharePoint applications. For example, you might have an issue with Excel Services and may want all of the Excel Services logs into a separate file while you investigate the issue.
Project Professional 2013 Reports
With the preview version out I was able to play around with Project Professional 2013. Like always this is the preview version so things might change.
When playing around with Project Professional 2013 I came by a new feature that I just had to blog about. Reports in Project Professional were not always of best use. They had their uses but in my experience I hardly used them.
In Project Professional 2013 however Microsoft decided to do something cool.
They basically made a report dashboard. There are a few pre-defined reports to choose from:
- Project Overview
- Work Overview
- Burndown
- Cost Overview
And much more…
One option in particular is very cool. Creating your own report by the use of a pivot table mechanism. This makes it very easy to create a report in a few clicks. Add that with all the different options available to you, you have the ability to create a really useful reports in mere minutes.
This for me personally is a major improvement on Project Professional 2010. It enhances the ability of Project Managers to get good and valuable reports. In this dashboard you can do some cool actions. Like for instance, adding your company logo to your report.
This report capability also gives you the ability to rearrange all the fields. This is very handy for any Project Manager. How many times have you been fiddling with a report to fit everything on one page. This time is has been made really easy.
Next to that you have the option to add charts, table and textboxes and much more…
Next to that you have the option to add charts, table and textboxes and much more…
All in all too much to sum up in a small blog post. I would say experiment with it. In my opinion this greatly increases the usability of Project Professional 2013 for any Project Manager. A really good use for these reports would be a Checkpoint Report or Highlight Report.
I am really impressed by this feature, and what it can do, and what it means for anyone that needs to report on a project. The easy to use prebuilt reports already cover the most of report a Project Manager needs.
I am off to see what else Project Professional 2013 has in store for me. But for now consider me impressed.
via SpeakingSilent » Robin Kruithof http://speakingsilent.wordpress.com/2012/07/30/project-professional-2013-reports/
|
I am Robin Kruithof. I am working at CXS in the Netherlands as a Microsoft Project Consultant. My passion lies in Project Management and everything in the Project Management domain.
This article has been cross posted from speakingsilent.wordpress.com/ (original article) |
#ProjectServer #PS2013 Log Level Manager #SP2013 #SharePoint #MSProject #PowerShell
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
There is new feature in Project Server 2013 called the Log Level Manager that enables you to track certain entities such as Projects, Resources and Tasks etc. Once configured, all activity on the farm for that particular entity, depending on the logging level set, is logged in the SharePoint ULS logs.
More details can be found here:
http://technet.microsoft.com/en-us/library/ff631142(office.15).aspx#section16
The log level manager is configured using PowerShell, the Project Server 2013 preview PowerShell commands can be found here:
http://technet.microsoft.com/en-us/library/ee890097(office.15).aspx
For the purpose of this blog post I have enabled logging for one test project, the project is called PMPSTest1 and the project GUID is 35cafba6-38d6-e111-9923-4c809328175b. Below you can see the PowerShell commands used to set up the logging for this one project:
Notice the refresh command, this is required to update the cached list of entities to watch.
As mentioned above the log level manager writes the logs into the SharePoint ULS logs, an example can be seen below:
An example entry:
LogLevelManager!PWA:http://vm657/PWAClassic, ServiceApp:Project Server Service Application, User:i:0#.w|cps\paulmather, PSI: Start checkout of project ’35cafba6-38d6-e111-9923-4c809328175b’ by resource ‘f8a06617-38d6-e111-bf72-00155d1463b9′ to store ‘WorkingStore’. Project:35cafba6-38d6-e111-9923-4c809328175b Original TraceLevel:Medium 9f6fbd9b-85f6-e003-5b7a-17f60ec5f059
The SharePoint ULS logs aren’t the nicest of log files to look through at the best of times, never mind trying to look for logs regarding the specific Project Server entities that you are tracking. I will create a simple PowerShell script to take all of the log level manager entries from the ULS logs and place these into a new text file/s. This will enable you to view all of the Project Server log level manager entries without the other SharePoint entries.
The log level manager is very useful for auditing / tracking activity for a certain project, task or timesheet etc. It would not be recommended to enable verbose logging for all entities in Project Server though!
SharePoint (and Project Server) Shenanigans 
You must be logged in to post a comment.