This project is read-only.

Install at the root?

Nov 6, 2008 at 3:21 PM
I am about to start out installing the October release to my existing SharePoint solution.  At present I have a web application called Moss and I access my Moss homepage at the following address internally https://moss/pages/default.aspx.

Now I understand that I need to install PKS at the root of the web app.  Do I therefore need to install this directly to https://moss for it to work correctly or should I create another site collection which would then take me to https://moss/sites/pod/Pages/pkshomepage.aspx assuming that I call the site collection 'pod'. 

If I have to do the former when I run the install should it be as follows:

ssm.exe install pksfull.xml https://moss

If I do will this interfere with the content I already have on here?

I tried it first of all creating a new site collection inside of https://Moss as I need students to be able to access the podcast site through SharePoint. This gave the address as shown previously as https://moss/sites/pod/Pages/pkshomepage.aspx but certain aspects of this do not work correctly and I am sure it is because it needs to be installed at root level.  Am I correct in my assumption here?

Any further tips useful

Nov 7, 2008 at 7:44 AM
If any of the developers could give me a quick answer on this one I can get moving.  I'd like to start off on the right foot if you know what I mean.

Nov 7, 2008 at 2:05 PM
You guys must be busy today, anyways i am at the stage of changing the default.master to the PKSMasterPage.master and am a little concerned with regards to how this will affect the look and feel of the rest of my solution.  Will only the PKS pages reflect the new PKSMasterPage.master look or will all pages under this change?
Nov 7, 2008 at 2:29 PM
OK so that doesn't work because it changes the default.aspx page under https://moss/pages/default.aspx to the black of the PKS master page setup.  How can PKS coexist within an existing webapp without have to change the master pages etc?

I really want this to sit inside our existing MOSS 2007 solution as it will be great for students to access podcast from within and outside of school.

Anyone any ideas?
Nov 7, 2008 at 4:53 PM

You can use your own master pages, update the layouts and redeploy the web parts within the site collection.

The only required elements should be that the script manager is in your existing master pages and the controls in the web.config.

Try adding or verifying that the <controls> items are in your web.config



<add tagPrefix="asp" namespace="System.Web.UI.SilverlightControls" assembly="System.Web.Silverlight,Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />



Try adding or verifying these entries  your custom master page


<asp:ScriptManager ID="ScriptManager1" runat="server" />


<script language="javascript" type="text/javascript" src="/ContentRatingResourceFiles/Scripts/Ratings.js"></script>

Nov 10, 2008 at 10:04 AM
Thanks awinters, I have a minor issue with my pkshomepage.aspx at present which is showing the following error:

Error Creating Control -g_d6b62303_f30d_40f2_aacb_9091133ac225b Request is not available in this context.

This error appears where the "Podcasts" web part should appear.  Any reason why this should happen and perhaps how I could resolve it.  I know the podcasts are there and that the thumbnail is created because I can see this in the PKS Podcasts list.

Additionally, and I have noticed this repeated by someone else without resolution on the Podcasterdetial.aspx page there is a QueryString error as shown below.  Any idea what this could be?

QueryString of key "csId" not found

Nov 10, 2008 at 5:16 PM

Regarding your question about the path to use with ssm.exe, you should definitely use  ssm.exe install pksfull.xml https://moss/sites/pod as I reported in this thread. Now that being said, it resolved many of my issues, but I still don't have PKS working correctly....

Nov 12, 2008 at 11:15 PM
Hi Chris

Here are the quick steps:


-> Point the SSM installer to the root of the site collection where PKS will be installed http://server/sites/subsite

-> Updated each page with the CBQ web part and update the location of the XSL - In order the update the XSL paths in the CBQ web part rather than making via shared properties. The web part needs be exported, next open the exported web part via notepad and update the paths to point to the correct site location. 


The updates that need to be made are:

 <property name="ItemXslLink" type="string">/Style Library/XSL Style Sheets/PKSItem.xsl</property> <property name="MainXslLink" type="string">/Style Library/XSL Style Sheets/PKSMain.xsl</property>

See this thread for more info: