• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8452
  • Last Modified:

Linking Project Server 2003 and Project 2003 Professional

I am new to Project Server 2003 and Project 2003 Professional. My customer has been using Project 2003 Standard on a single client computer for their Home Building Business and has many .mpp files created.

I recently installed a 2003 SBS w/exchange for them and have successfully installed Project 2003 Server onto it using a 51page guide titled "Project Server 2003 on SBS 2003 - Courtesy of Chris Jones - All rights reserved by the Author" This guide was perfect and have Project Server 2003 running perfectly in conjuction with EXCHANGE and sharepoint services. I do understand that it is not recommended to install Project 2003 Server on SBS 2003, but this guide allowed the installation perfectly and the extended ENTERPRISE features of Project 2003 is not something that is needed.

What we need is to allow the existing client who is using Project 2003 Standard (I upgraded this client to 2003 PROFESSIONAL) to be the Administrator, as she already does the creation and management of all the Project files. Any additional users will use Project Web Access to view and add to the existing data that the administrator has created in Project Professional 2003

The QUESTION:
How do I import these existing .mpp files into Project Server 2003 so that they can be view and manipulated with Project Web Access and syncronize with the single Project 2003 Professional data that the administrator puts in.

This is an urgent matter. Thank you
0
ZionTech1
Asked:
ZionTech1
  • 27
  • 11
  • 8
  • +1
2 Solutions
 
dbase118Commented:
Open the project plans using the Open option on the File Menu. Then select Open from File – ODBC, locate the project plan, and then click Open. You will then need to transform the project plans to enterprise project plans by using the Save As option of the File menu or by using the Import Project Wizard available from the Tools menu (select Enterprise Options, and then Import Project to Enterprise)
0
 
BembiCEOCommented:
> I do understand that it is not recommended to install
Put enough RAM into the server (what can never be enought if all these services are running on the same machine).

If you import the projects directly from the files (you have an option to do so within the tolls - enterprise options), you will also import all the resources into the resource pool (if you are the admin and allowed to). This may result in double and tripple resources, whenever there are differences in spelling them within the resources. Also the resources are setup simply as MS Project accounts (no windows authentication). It might be an idea, not to allow creating resources and the setup th resources manually (MSP - Open Enterprise resource pool). Then you have to reassign all resources and delete the local project resources before you save them.

This might be a little bit more work and depends on your current projects, but on the other hand, you may have to correct a lot of resource conflicts caused by imported resources. But it keep your resource list clean.
0
 
ZionTech1Author Commented:
Bembi

Do you agree with dbase118's process or are you stating that dbase118's process will create resource conflicts. If so and you believe I should use your process, can you please step by step it for me as I am new to Project Server 2003 and Project Professional 2003

Thanks
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
ZionTech1Author Commented:
dbase118

When I try to use your process the "All Projects.mpp" file is not visible under SELECT DATA SOURCE. To reiterate, the customer has been using Project 2003 STANDARD and has files called "All Projects.mpp", resource.mpp, and 55 other files name with "the address of the build site".mpp . I need to get all that data into the Project Server 2003 so that the STANDARD user that I have upgraded to PROFESSIONAL can still be the administrator of Project and also be able to have other users PWA in to see the data and manipulate on the Project Server 2003 server.

Thanks
0
 
MSProjectGeekCommented:
I do NOT recommend the save as option, you will have problems with your files.  

Instead, use Tools - Enterprise Options - Import Project to Enterprise and follow the wizard settings.  Although you'll have to mess around mapping your resources to the enterprise resources (unless they have exactly the same names), it's worth it in the long run to avoid future problems.

FYI, this is a question on the 74-131 exam which I have passed - the official answer is - use the import tool.
0
 
ZionTech1Author Commented:
Below is the following error message I get after doing the following procedure on the client computer running Project Professional 2003:
1. Start->Programs->Microsoft Office->Microsoft Office Tools->Microsoft Office Project Server Accounts
2. Clicked ADD and for the account name typed in:  deb.blanchard (Name of XP username on client computer and matched in Active Directory on server, I also put this in during the setup of Project Server 2003) for the Project Server UR I typed: http://fireserver/projectserver and tested the connection with the TEST CONNECTION button which returned the result "Project has successfully conntected to the specified server."
3. Under the "When connecting" option I chose USE A PROJECT SERVER ACCOUNT: and typed in the user name : deb.blanchard (which is the logon username to the XP client and also matched in the AD on the server). Closed window
4. Started Project Professional 2003 on the Xp Client and was prompted by the "Project Server Security Logon" window where I typed in the password that had been setup in AD on the server and also for the XP client.
5. Received message below. Please repsond ASAP
6. If I choose USE WINDOWS USER ACCOUNT for WHEN CONNECTING under the Project Server Accounts Account Properties I get a different error which is also below title. WINDOWS USER ACCOUNT ERROR.

"The Project Server database is unavailable.

You can't access the database for one of the following reasons:
There is a problem with the enterprise global template inthe database.
You do not have sufficient permission to access the enterprise global template
Network problems are preventing access
Project Server does not have enterprise features enabled.

Try to connect to the Project Server again. If the problem persists, contact your server administrator

WINDOWDS USER ACCOUNT ERROR
You are attempting to log on using a Windows
user account, but you do not have a Windows
user account on this server You need to change
the account in your profile or contact your
server administrator to setup your Windows
user account on this server. (5002)

Thanks
0
 
ZionTech1Author Commented:
Really need some timely input please. I can't beleive there are no Project experts out there.
0
 
MSProjectGeekCommented:
Jeesh,

3.  Getting the message "Project has successfully conntected to the specified server." only tells you that there is a project server at the end of the URL, it says nothing about whether the account you entered has PERMISSIONS to do whatever it is you want them to do on the server.

6.  If the user you are trying to connect as has their PWA account set to Project Server Authentication then ONLY that method will work - you have to decide which way you will work - if you have a choice, I strongly recommend Windows Authentication.  Make sure the settings match both ends.  You must type their setting into PWA Admin manage Users and Groups / Users as Windows Authenticated and then type in their domain\username

So, user Fred Bloggs is set in PWA Admin users and groups as Windows Authenticated.  You type their data into the Project Pro Account setup and then try to connect from the PC that you have logged onto as them - I assume this is where you're trying to go?  Things that will cause the messages you are getting...

Your Project Server URL is not in IE trusted sites.
Trusted Sites security is set to something other than Low
The User does not have membership of a group that has permission to connect to Project Server using Project Professional - By default they are Team Members but as such they will not be able to connect using MS Proj Pro, you'll have to add them to the Project Managers group at a minimum.
0
 
ZionTech1Author Commented:
Thank you for the response MsProjectGeek. I will try those options ASAP.
0
 
BembiCEOCommented:
Just to respond, as most ogf the things are said.

> Do you agree with dbase118's...
I would more following MSProjectGreek to use the import tool rather than just saving the project, as you may run into resource salad. Resources should only exist on the server. Same name helps during import.

1.) OK
2.) Name of the connection does not matter. In initial mode, you have only the administrator account, which is a MS Project account. Logon with the administator account into Web-Access (URL into your browser). There, logon with administrator and your Password (you defined during setup). Goto ADMIN and select Users and Groups. There you can add additional users, either as MSProject Users (UserID + Password) or as windows account ( DOMAIN\USERNAME ). Not that the Username is a NETBIOS name. DOTS are allowed, but not a good idea as not completely NETBIOS conform!!! There, you can setup your account (either as MSProject account or Windows account and assign a role for this account. If you assign a role, which is not "Administrators", note, that there is a general right, which projects can be created / published: See Web Access --> ADMIN -> Server configuration.

You can then logon (MSP Pro) with your newly created account (or also with the admin account). Open Enterprise - Options - Enterprise resource pool to define resources (which gets automatically a logon account as Team Member). If you want to see your accouts as resource, you have to define your account (same name) again here.

Note: AD accounts do not have something to do with MS Project logons. MS Project logons are independend from your windows account. You can use your windows account, if you select windows authentication (In Web Access) and den NETBIOS name (not the kerberos name, which looks like an email address). Windows authentication allows a automatic logon and a lot more.

4.) As you have selected USE A PROJECT SERVER ACCOUNT --> OK
5.) If you have not setup a logon account in Web-Access, you have to logon as administrator (as this is the obnly existing account).

0
 
ZionTech1Author Commented:
Ok. I after unsuccessfully trying to login with MS PROJECT PRO to the Project Server over 100 times with either Windows Authentification or Project Auth. I read "Title: Cannot log on to Project Server 2003 with AD user accounts" in EE and found out that I need to switch the Server Configuration under PWA ADMIN to "Enable Enterprise Features".

Having enabled this, MS Project Pro client computer logons on with Windows Authentification but not Project Auth, BUT...... as soon as it passes throught Windows Auth. I get the following error:

Microsoft SQL Server Login (Window Title)
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

(why the hell is this so difficult?)

Please help.
0
 
MSProjectGeekCommented:
Sorry we missed that but enabling Enterprise Features is like saying you have to turn the key to start the car.

Anyway, you need to add the URLs for the project server and the sql server to your trusted sites and then set the trusted sites security level to low; that's all in IE under tools-internet options-security, it's fairly intuitive.

note that you'll need to uncheck the box that requires https for trusted sites - lower right of the add trusted sites box - and the URL's you enter should be something like this...

http://FQservername/projectserver  <== strip everything after prohject server off this url
http://FQservername                      <== for the SQL server

The reason you need the SQL server too is that Project Pro negotiates with the Project Server for access to a project and if you have permissions, it then sets up a direct connection to the database so that the actual load and save is done directly to from and to the SQL server.

If it wasn't difficult, we couldn't be experts <grin> but I agree, setup seems to have been written by Atilla the Hun's coding dept.
0
 
ZionTech1Author Commented:
Thanks MSProjectGeek I will try that. Thanks for the tech and emotional support :) !
0
 
ZionTech1Author Commented:
What is the FQ in the FQservername. Do I need to put http://FQ(myservernam)/projectserver ?
0
 
ZionTech1Author Commented:
I went to Internet Options, then under SECURITY, then selected on TRUSTED SITES. The security level was already set on low as I had set that earlier. Then I clicked on SITES, and added http://FQfireserver/projectserver and https://FQservername . I put the https one in there because it said that a path like that already exits. I unchecked the https option. So under Sites I have:

http://fireserver
https//fireserver/projectserver
http://FQfireserver/projectserver
https://FQfireserver

and I still get the exact same error. My certificate is installed and I can successfully log into PWA from this client computer also. The only thing I see that is strange is that I can get into Sharpoint Central Administration from the client computer, but not Sharepoint Services Home page i.e. http://companyweb it just goes the no server found type of page like when you don't have an internet connection and try to get on a webpage. Sharepoint services homepage works fine on the server.
0
 
BembiCEOCommented:
If you get an SQL Server error, it may be a sign, that the connection between Project Server and SQL Server is lost or invalid. The Installation creates two SQL server user MSProjectUser and MSProjectServerUser to connect to SQL server. Also a ODBC setting is created by the setup. To recreate the connection to SQL server, there is a tool with in the ProjectServer\Bin\1033 folder, there are two tools, one for the recreation of the COM+ components, the other for the recreation of the connection settings for the two server accounts. A better tool is the EditSite tool, you can download from MS. This is a more powerful tool to recreate the server accounts as well as the ODBC settings at once.

Also, you may have a add another user to SQL server. This user depends from your installation. Igf your ProjectServer under IIS is running under Networkservices identity (default), you have to make sure, that this account is setup within SQL server and permissions for the ProjectServer Database within SQL. If you have another identity for the Application Pool, your project server is runningin, you may have to add this identity account to SQL server.

Just have a look, which identity is setup for the application pool for project server and see, if you can find this account in SQL Server.

Usually, everything is setup by the ProjectServer setup, but any change to these settings may destroy the functionality.
0
 
MSProjectGeekCommented:
FQservername was my way of indicating that you needed to enter the 'Fully Qualified Server name' so you might have to add http://myservername.myorg.com/projectserver - don't stick FQ in front of it!

Bembi may also be right that you need to run the com+ tool from the folder Bembi mentioned.  To do that you'll need to know the account names and passwords that you set up in the first place.  These account are supposed to get specific permissions to access the systems.

If this still doesn't work then I'd go back and re-read the install instructions to make sure that you've set it all up as it says, the next thing I'd check is the proxycfg settings.

I had assumed that you'd run through the install wizard and got sucess messages?

MSPG
0
 
ZionTech1Author Commented:
When I did my installation guide. I had ZERO problems setting up.
1. Did the PSComPlus.exe file and input fireside\deb.blanchard and the password into both fields and updated. Did not work.
2. Removed the FQ mix up paths under TRUSTED SITES and input http://fireserver.firesidehomesinc.com/projectserver. Did not work.
3. Do I find the Application Pool under SQL Server Enterprise Manager? And what exactly do you want me to find under SQL Server Enterprise Manager if that is the place?
4. Under SQL Server Enterprise Manager I have to SQL Server Groups
    a. (local)(Windows NT)
    b. FIRESERVER\SHAREPOINT (WINDOWS NT)

5. Does it matter if you logon to client as (this computer) or (domain). I logged as both and get same SQL error as mentioned above.

0
 
BembiCEOCommented:
1.) The PSCOM tool is to define the Identity of two COM+ component for SharePoint and OLAP Server. The account is usually the account, which is usually used by the application pool. There is a second tool CONNINFO within the same folder to setup the SQL Server users (MSProjectUser + MSProjectServerUser).

The EditSite Tool does the same, but is able to additionally recreate the ODBC connection definition.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

3.) The ApplicationPool can be found within IIS 6.0 Administration Snap In. there you will find an application pool (a folder beside the Sites folder) for SharePoint and an additional Application Pool for Project. If you right click these application pools, you can see (and change) the identity. The identity is like a service account, but you can run each web-site under a different identity by changing either the logon account of the application pool or to change the application pool setting of the web-site, project server is running in.
Usually, Project Server is installed under Networkservices identity (MSProject2003 Application pool and COM+ components). But as Windows controls the the passwords for this system account, it may be broken by a few uncontrolled clicks. Additionally, you need the IIS6 resource kit tool MetaEditor to find out the password for this account. But if the password is wrong, you will get logon failure event logs within the security log (if failed logon log is enabled within the policy)

4.) If project server (IIS application pool + COM+ + services) is installed under Networkservices, you will usually find also the YOURDOMAIN\Networkservices in SQL Server under logon accounts. If you have choosen to use a dedicated service account during installation, this account should be setup in SQL server. A usual situation for a lot of trouble is, if this service account password is changed, as used by a lot of different services.

I assume, the (Local) account in SQL server is the local administrator. The other account maybe an account for Sharepoint? This maybe also the account for project server, as it is a good idea to use the same account / identity for SHarepoint and ProjectServer. But have a look at the service accounts of the Project Server services and the service account of the one SharePoint service, you can find under services.

5.) Yes, it does matter as you may not able to resolve windows accounts if you are not logon within the domain. To use project server, your computer should be member and also logged on within the domain. It may work with a project server account, but I would assume, it will not work with windows authentication.
0
 
ZionTech1Author Commented:
4. Under SQL Server Enterprise Manager I have two SQL Server Groups which is under Microsoft SQL Servers
    a. (local)(Windows NT)
    b. FIRESERVER\SHAREPOINT (WINDOWS NT)

These are not accounts I was explaining. These are SQL Server Registrations if that helps

I am confused now Bembi from where to go now from here.
0
 
BembiCEOCommented:
OK, open both (with Enterprise Manager) and have a look at the databases within them. Seems to be, you have one SQL server and a second (MSDE) instance for Sharepoint. The database which host ProjectServer, you will find a database, named ProjectServer. Open Security, there you find the logon names and you will find a few logon names like Predefined\Administrators, MSProjectServerUser, MSProjectUser, NT-Authority\Networkservice and so on. The last three are usually installed by MS Project Server. MSProjectServerUser and MSProjectUser exists anyway, a third account depends on the installation. If the project server was installed with defualt options, then it is the NT-Authority\Networkservice account (and the COM+ idendities and the IIS Application pool "MSPS2003AppPool" identity as well as the service account of the Project Server services will use it).  

Download the EditSite Tool above, this tool will usually also determine, which SQL Server instance is responsible for your project server. Retype passwords for the two users (MSProjectServerUser, MSProjectUser) and click "SAVE" and the tool will recreate these accounts as well as the ODBC driver settings. It maybe that this is all, what you may have to do to repair the SQL Server connection.

For the ODBC driver (Site Information on the left side), the settings should be:
DSN Name: PC11DSN
Query timeout 1200
Session Manager = Name of your SQL Server
0
 
ZionTech1Author Commented:
Bembi I will be attempting your instructions in 30mins. THANK YOU SO MUCH
0
 
ZionTech1Author Commented:
Status of ProjetServer Reports:
Virtual Directory: PASSED        Primary Admin: Administrator
MSADC: PASSED                    Enterprise Enabled: Yes
Registry: PASSED                   Total Projects: 0
Database: FAILE                     Active Resources: 3

Result Information
The Project user is not a member of the MSProjectRole. This was ran off the Project 2003 Server (SBS 2003 Server)
0
 
ZionTech1Author Commented:
the MSPROJECTROLE MEMBER had the User Name: MSProjectServerUser. I changed it to MSProjectUser then tested and No errors were encountered. I typed in the passwords to match the same one I use for the use that Iam trying to get connected: deb.blanchard  or fireside(domain)\deb.blanchard(username).

This still has not changed the problem
0
 
ZionTech1Author Commented:
I found this from Microsoft when I googled "SQL Server Error: 17" It should my exact error and problem concerning Project Server 2002 and 2003 http://support.microsoft.com/?scid=kb;en-us;837653

Project Server 2003
If you are running Project Server 2003, use the ConnInfo.exe tool to edit the registry of the server to use the IP address of the computer that is running SQL Server. To do this, follow these steps: 1. Locate the folder that contains the ConnInfo.exe tool, and then double-click ConnInfo.exe.

The ConnInfo.exe tool is located in the Drive:\Program Files\Microsoft Office Project Server 20031\Bin\1033 folder of the computer that is running Project Server 2003. To download the ConnInfo.exe tool, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=1d30b672-baa0-4030-b036-323b216d7264&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=1d30b672-baa0-4030-b036-323b216d7264&displaylang=en)
2. In the Project Server 2003 Connection Information dialog box, click either Single database configuration or Partitioned database configuration.
3. In the SQL Server box, type the IP address of the computer that is running SQL Server, click Save, click OK, and then click Exit.

This is done work AT ALL. It when I had the IP address of the server running SQL in there it wouldn't even let Project Pro 2003 connect or PWA!

I am fixing to loose it

0
 
ZionTech1Author Commented:
I have now discovered I can get in using MS Project Pro 2003 through "Use Window user account" and "Use a Project Server Account:", but I still get the SQL Server Login Error both ways

Microsoft SQL Server Login (Window Title)
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
0
 
MSProjectGeekCommented:
My SQL Guru says....

"Answer is simple

Project Pro after connecting to PWA server, spins up an ODBC connection to SQL server. This error is due to ODBC ports being blocked and/ or the Project authentication does not have sufficient connection credentials to open the ODBC backdoor."

I think you should be looking at the accounts you created - the ones COM+ uses and checking their permissions in SQL - also you did set SQL for mixed mode authentication when you set it up?  Check the permissions for the accounts on the projectserver database.

Use these documents...  http://www.microsoft.com/downloads/details.aspx?FamilyID=ca99b5e3-0478-4ac3-a230-c4f2d82096c1&DisplayLang=en

MSPG
0
 
MSProjectGeekCommented:
I Googled SQL Error 17 and got these ideas...

Severity level 17 indicates that SQL Server has run out of a configurable resource, such as locks. Severity error 17 can be corrected by the DBA, and in some cases, by the database owner.

Another cause can be Windows firewall which will prevent you from connecting to the database hosted on different server. Here is what you can do.
Start menu -> click on run and type -> wscui.cpl -> Select Exceptions -> Add port -> Enter Name: SQL SERVER Port Number 1433

MSPG
0
 
BembiCEOCommented:
The two roles MSProjectServerUser and MSProjectUser can have any password, the only condition is, that you config them with the MS Project Server tools CONNINFO or with EditSite, so that MSP knows the correct passwords, which the tools sets up in SQL server. No user user is using these passwords, they are handled internaly. MS Project Server uses these two accounts, you connect itself to the SQL Server or to redirect user requests.

Also note, that SQL Server is mostly NETBIOS (or Pre Win2000) orientated, that means, that using charactars, which are not explicitely allowed for NETBIOS names may work or may work not. For NETBIOS Usernames and Passwords, you should only use numbers 0-9 and characters a-z, avoid any special characters as underscores or dots or whatever.

To correct the ODBC connection setting, use EditSite Tool, to set the Passwords as well as the ODBC connection at the same time.

The error message above will show the source of the error (eitehr a machine name or a user name). So have a look at this message again (with event log), which machine produced the error. It it is the server, the reason is mostly the password or the ODBC issue.

0
 
ZionTech1Author Commented:
I did not setup mixed mode for the Authentication Mode for SQL Server 2000. I uninstalled everything and am reinstalling again choosing Mixed Mode.
0
 
ZionTech1Author Commented:
After uninstalling Project 2003 Server, SQL Server 2000, and SQL Server 2000 (SHAREPOINT) I reinstalled SQL 2000 SP1 then did SP4 update, but I cannot see my Sharepoint services. In Enterprise Manager for SQL server It shows the FIRESERVER\SHAREPOINT (Windows NT) instance under SQL Server Group, but it will not start. I suppose SQL Server 2000 (SHAREPOINT) needs to be reinstalled, but where do I get that install from and is there a special way of doing it?

On Jobsite now. Please help!
0
 
ZionTech1Author Commented:
Below is the guide I mentioned above that I used to install Project Server 2003 to SBS 2003. I told to me to incorrecly choose the other mode instead of MIXED MODE

www.ziontechs.com/projectserver2003  There is a link to the PDF on that page.

Still need help with installing Sharepoint Services or the SQL for it as it will not run or can be seen now after uninstalling SQL 2000 (SHAREPOINT) Not know where to get the install for that. Tried Reinstalling Sharepoint Services with SP2, but did not work and did not start the SQL instance under Enterprise Manager
0
 
MSProjectGeekCommented:
Just a quick comment - there are specific weirdities for installing with SBS - is that what you're doing?  I know that SQL MUST be in mixed mode for all the installations I've ever done.
0
 
ZionTech1Author Commented:
yes. That guide I have above is supposed to remedy the weirdities, but it did not tell me to install in Mixed Mode. May be a mistake. I went ahead and used SQL 2000 SP2 to install a new instance of the SQL 2000 called SHAREPOINT. I am updrading with SP4 now. Then will use WSS Central Adminstration to connect to the Application Pool of it.
0
 
BembiCEOCommented:
SQL Server must run in mixed mode as the MSProjectServerUser and MSProjectUser account are using this mode. But this is simply an option of your SQL Server properties. Open SQL Enterprise manager and select your server, right click --> security, ther you can change the mode.

Install SharePoint into the same SQL Server, not into the MSDE. During setup you have the choice to select "remote database" or just run
setupsts.exe remotesql=yes to preset this setting

See:
http://support.microsoft.com/kb/555062/en-us
0
 
ZionTech1Author Commented:
Finally. I will explain what I did in detail soon, but now I am to the TOOLS, ENTERPRISE OPTIONS, IMPORT PROJECT to ENTERPRISE Wizard. As stated before the user has a file called ALL PROJECTS.MPP and 55 other files with the address of the home (i.e. 901SL Thurn.mpp). The User allways opens ALL Projects.mpp and it looks like all the other .mpp files can be seen from this ALL PROJECTS.mpp. Do I import this one ALL PROJECTS.mpp or other the others seperate or what. Confused at this point. ALMOST THERE!!
0
 
ZionTech1Author Commented:
I went ahead and tried to import the ALL Projects.mpp file which obviously was connected to the other 55 .mpp files and it wouldn't let me. It told me to disconnect the resource pool connected to it. I did that then resaved under a different name and imported that. That worked. I can see the data inside PWA under Projects, but I cannot see the details and phases like in Project 2003 Pro. I also have the 55 other .mpp files in a folder on the server and I can see that the .published on the Project 2003 Server is referencing back to those .mpp files on the server. When I hold my mouse over any of the Project Server Icons in the Indicator Column in Project 2003 Pro it says "This inserted project is embedded from "(my UNC path from the Project Pro Client to the .mpp file on the server)". How do I get those into the server so they are not pulling from the .mpp file, but from the Server.

Summation:
1. How do I see the details and phases like in Project 2003 Pro when using PWA?
2. How do I import the rest of my .mpp files to be on the server connected to my main Published project that has views and connections to the other .mpp. Are these called resources?
0
 
MSProjectGeekCommented:
Wow you're looking for value from these 500 points!

1.  Collaborate-Publish All information - basically, the data doesn't make it across to the PWA database unless you do this; you can granularize the data between - New and Changed Asssignments and/or Project Plan.
2.  If you have linked tasks bewteen projects then you'll have to import the projects to the server and then correct the linkages.  I'll have to look it up but there's a prefix that implies 'on the server', I think it's <>\ but I'll check and post back.
0
 
ZionTech1Author Commented:
Well, the title of the Question is "Linking Project Server 2003 and Project 2003 Professional" and I rarely get and value from EE anyways, because you are obviously not there to answer all of them MSProjectGeek ;). Thanks for all your help. Bembi too!

1. Does this Collborate = Publish ALL Information process permantly import the sub projects (other.mpp files) into the mail Project I open that shows these sub projects (other.mpp files) so that I do not need the .mpp files anymore?

2. Not sure what you are describing here. What are linked tasks?
0
 
BembiCEOCommented:
What you have is a master project with linked Projects. I have not just tried that, you may have imported the master projects, and the sublinks are as they where before, a link to a local file.

I would say, that you have to import all single files and after importing them, you can create a new master file on the server and relink all subprojects into the new masterfile.

Ususally, the master project do not need a link to the resource pool (a local resource file). You can import the resources from that file and MSP should replace the resources by the enterprise resources while importing the project files.
0
 
ZionTech1Author Commented:
Thanks you Bembi and MSProjecGeek. You have answered and solved all my problems. I am splitting points. I will explain in detail if it still lets me after awarding points. If not, then I will soon have a PDF explaining all that I did at
www.ziontechs.com/projectserver2003 to help others
0
 
MSProjectGeekCommented:
"1. Does this Collborate = Publish ALL Information process permantly import the sub projects (other.mpp files) into the mail Project I open that shows these sub projects (other.mpp files) so that I do not need the .mpp files anymore?"

When a project is imported / created and saved to the project server (you will see the filename ends in '.published', it's then in what I call the main database; technically it's not visible in Project Web Access (PWA) (but MS has messed with that so sometimes you'll see it (in PWA) and sometimes you won't).  If you want to make the resources see their assignments in their PWA timesheets you need to do a Collaborate-Publish assignments, if you want to guarantee that the project is visible in PWA (project Center and View a Project) then do a Collaborate-Publish Project, if you want to do both, then do a Collaborate-Publish All Information. Once you import the .mpp files and save them to the server then you don't need the mpps any more but BEWARE - read on.  

"2. Not sure what you are describing here. What are linked tasks?"

When you form a dependency between 2 tasks, the first one is the predecessor and the second one is the sucessor; by default the Gantt chart view includes the predecessor column and you will see that it normally contains the Task ID of the predecessor.  I assumed from your earlier comments that you were taking this one step further and setting predecessor tasks that were in other projects.  This is why I said BEWARE, If you imported a project to the enterprise, the predessor tasks may still be referring to the tasks in the .mpp files which is allowed, to change them to refer to the tasks on the server (assuming you imported the projects containing these predecessor tasks), the format needs to be changed to <>\PredecessorProjectName.published\TaskID# where '<>\' indicates that the project is on the Project server.
0
 
ZionTech1Author Commented:
After I force the .mpp file to use it's own resources under TOOLS, RESOUCE SHARING, so that I can import (publish) in to Project Server, I then move the .mpp file from it's know location so that my "Master Project" that is .published, and has all my main tasks or jobs or all other .mpp files (however you want to say it) forces me to find the file again. I then relink it to the .published version of the old .mpp file. When I move my mouse over the ICON in my MASTER PROJECT for the task it shows that is it an embedded file to the server with the <>\ symbol. Do additionally have to Collaborate-Publish All information for the PWA people so see all info?

Secondly regarding the resource.mpp file, which is the largest file. How do I import that to the server properly. When I try the same method as the other .mpp file. It brings up a windows talking about it being a resource pool.  I know this is a very important file and don't want to import properly. Thanks for all your help guys. These last questions are just the icing on the cake.
0
 
MSProjectGeekCommented:
The <>\ symbol means 'a project stored on Project Server' but it doesn't mean that it's visible in PWA.  Once you Collaborate-Publish then you can see the project in PWA.  I think of Collaborate-Publish as meaning that I'm publishing information to the PWA database.

If you had a separate resource file then the best thing to do is open it and use Tools-Enterprise Options-Import Resources to Enterprise.

Beware that there was a problem where resources get double-counted if you save and publish a master plan to Project Server; actually this is disabled by default in the Admin settings of PWA.  It won't break the system but it means that My assignment is double-counted, once for the project I'm assigned in and a second time when that project is made a sub-project of the master project.

Icing!  This is the sculpture on the third tier of the cake!!!
0
 
ZionTech1Author Commented:
So, once all my files are .published do I have to worry about Collaborate and Publish anymore for PWA? I thought Collaborate-Publish only works on .mpp files. Isn't it supposed to automatically update when the projects are .published so the PWA people are viewing the same info?
0
 
MSProjectGeekCommented:
By default, .published files are not Collaborate-Published!  Confusing isn't it?  You can set an option under Tool-Options-Collborate(Tab) that publishes the information to PWA every time the project is saved.

Actually .mpp files have nothing to do with the picture as they are stand-alone desktop files.
0
 
ZionTech1Author Commented:
Thank you for all your help MSProjectGeek. I am going to start a new question along the lines of what were are talking about now and going into more detail of PWA interaction.

Thanks again.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 27
  • 11
  • 8
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now