These are probably repeats for many of you reading - but based on personal experience there are still some people that haven't got these messages:-
Technorati Tags: Project Server 2007
Hi Brian. Why 'preferably Office SharePoint Server loaded first'?
Thanks for the blog, Alex.
In Project Server 2007 there is a feature called the proposals workflow that makes use of one of the built-in workflows of Office SharePoint Server. If you install Project first then this feature will not automatically work on PWA instances you have already created before you loas Office SharePoint Server - but will work on any new ones. There are a couple of workarounds - the first is to delete and recreate your PWA site - although this can lose any WSS data you may have created (issues, risks, documents and deliverables), and the second which I will probably blog about in the next few days does not risk losing any of you data.
Thanks for the question.
In the Tech Center, there is a passage that describes how PS 2007 can connect to 3rd party applications, and to SAP and Oracle instances out of the box. But nowhere is it described how this is performed or configured.
Would you know anything about this?
Great question Robert.
I'm not sure exactly which passage you refer to and "out of the box" means different things to different people. Out of the box Project Server 2007 has a set of APIs called the PSI - which can be used to interface Project to other systems - but with the flexibility of both Project and SAP/Oracle there is no instant interfaces. See the SDK for more details. There are also many partners who can add tremendous value here - some who have products that fill this gap.
I've configured the SQL Membership Provider forms authentication for Project Server 2007, I've created a new user and added him to a Project Server Group.
After a correct authentication by the provider, the form does not redirect to default.aspx page but to login.aspx again, without any error message.
I can only give you some general pointers here. First I would check that the user validates OK through the WSS user configuration - Policy for Web Application as providername:username - then check on a basic WSS site and finally check with the Project Server user configured as an admin to rule out any permissions issues. Hopefully one of these three steps should highlight where the error is.
Does any one has steps to add users in the SQL membership provider database using the Pjformsauthupdate.exe tools, the steps given in the Micorosft Document does not work, It give a error message that the tools works against SSL sites. If SSL is required how to configure SSL on the site.
2nd question first - the most straightforward way to change your site to SSL is to use Alternate Access Mapping under Central Admin, Operations and set your address from http://server to https://server - after you have added a certificate to the site through inetmgr of course.
If you use pjformsauthupgrade /? it should give a usage statement that may help with the required parameters - in case your documentation is out of date.
I performed a test install and then deleted everything, and redid the host project server in a server farm environment. Well now on subsequent installations it does NOT create the Draft, Published, Archive and Reporting databases. No matter what I've done I cannot get these databases recreated. It's like it has something in its brain to NOT recreate these dbs. Any help or copies of the DB structures would be appreciated.
If I have a single SPS 2007 server for my internal intranet and I want to add a Project 2007 Server, what is teh best way to do this? Make the new server an SPS 2007 farm member first and then install Project 2007 Server? I just need some basic guidelines to get started. Thanks...
Hi Shawn - If you try installing Project Server it should recognize the type of installation and do the right thing. Be aware however that the right thing may not be what you want. If the initial installation was standalone and used SQL Express then you will also get this for Project Server. Searching Technet.Microsoft.com for Project Server Techcenter should give some good documents on installation.
Ashish ran into an issue on April 17th related to an error with Forms Auth using the pjformsauthupgrade command. Here is the error I think he was seeing:
"C:\Program Files\Microsoft Office Servers\12.0\Bin>pjformsauthupgrade -log log.log -usersfile users.xml -url http://projectserverdev
Unable to read configuration for site http://projectserverdev.
PJFormsAuthUpgrade only works against SSL sites that have been enabled through Microsoft Windows SharePoint Services."
I've installed Forms Auth without using SSL many times. I'm wondering if this error is related to using the PWA path as the host header. To test this I created a second instance and used the http://machinename/instance as the URL. Same command and same users file as above and the command worked. Is there anything special you need to do to run the pjformsauthupgrade command on an instance that uses the path as the host header?
It's very helpful.
Thanks for sharing!
How to connect to a express database instance?
You should just be able to use the instance name - remember to set the instance to allow remote connections!
This is in response to Tony's post above. We are also getting the "PJFormsAuthUpgrade only works against SSL sites that have been enabled through Microsoft Windows SharePoint Services." error. We are not using SSL, but I'm don't understand what he means by not using PWA path as the host header. We use http://epmserver/pwa as the URL.