J
Joe Befumo
I've just started evaluating MS Project Server, and from a project manager's
perspective, it looks like the greatest thing since . . . whatever.
Unfortunately, I've hit two unrelated roatblocks.
The first one is resource related. I'm not sure exactly how this happened,
every resource seems to work fine except my own. I show up fine when I go
in through the web interface admin functions, however, when I try to import
a project from Project Professional, my name doesn't show up in the pull
downs for resource mapping. I tried deleting my account and recreating
it -- same problem. I tried deleting my account, then logging into my
workstation as administrator, but then Project Pro doesn't recognize the
domain administrator on the client as being the same as the 'administrator'
account on the Project Server. (Of course, once I delete my windows domain
account on the project server, I can no longer get in from my workstation.)
Seems like a Catch-22 -- can't seem to figure out why it's happening, or how
to work around it.
Anyway, I decided not to get hung up on this problem, and instead, to just
leave myself as a local resource, and publish the project. However, then I
encountered the following problem:
When I go to Collaborate|Collaboration Options, and try to test the
connection, I get the following:
=====================================
An error occurred while trying to access Microsoft Project Server.
This could be caused by the following:
a.. Low memory
b.. Some components might not be installed or registered on your computer.
c.. Some components might have become unstable.
Try the following:
a.. Free up available memory by closing any programs, projects, or windows
you are not using, and then try again.
b.. Reboot the computer.
==================================
When I try to navigate to the URL specified
(http://best-practices/projectServer), I see the Project Web Access page
just fine. I tried rebooting (both my workstation and the server), but that
didn't do any good.
The server machine is an 850Mhz with 512 Meg Ram. While marginal, it
doesn't seem to be the kind of problem that would be caused by hardware.
Any pointers would be appreciated.
Joe
perspective, it looks like the greatest thing since . . . whatever.
Unfortunately, I've hit two unrelated roatblocks.
The first one is resource related. I'm not sure exactly how this happened,
every resource seems to work fine except my own. I show up fine when I go
in through the web interface admin functions, however, when I try to import
a project from Project Professional, my name doesn't show up in the pull
downs for resource mapping. I tried deleting my account and recreating
it -- same problem. I tried deleting my account, then logging into my
workstation as administrator, but then Project Pro doesn't recognize the
domain administrator on the client as being the same as the 'administrator'
account on the Project Server. (Of course, once I delete my windows domain
account on the project server, I can no longer get in from my workstation.)
Seems like a Catch-22 -- can't seem to figure out why it's happening, or how
to work around it.
Anyway, I decided not to get hung up on this problem, and instead, to just
leave myself as a local resource, and publish the project. However, then I
encountered the following problem:
When I go to Collaborate|Collaboration Options, and try to test the
connection, I get the following:
=====================================
An error occurred while trying to access Microsoft Project Server.
This could be caused by the following:
a.. Low memory
b.. Some components might not be installed or registered on your computer.
c.. Some components might have become unstable.
Try the following:
a.. Free up available memory by closing any programs, projects, or windows
you are not using, and then try again.
b.. Reboot the computer.
==================================
When I try to navigate to the URL specified
(http://best-practices/projectServer), I see the Project Web Access page
just fine. I tried rebooting (both my workstation and the server), but that
didn't do any good.
The server machine is an 850Mhz with 512 Meg Ram. While marginal, it
doesn't seem to be the kind of problem that would be caused by hardware.
Any pointers would be appreciated.
Joe