Project Server Account Error

C

Christie

We recently migrated from an .mil LAN to a .com MAN. The project server
domain was changed. Now the project server URL will not connect from MS
Project. The message reads: "Project server error. The server returned an
error while processing your request. The error could be caused by one of the
following: The URL specified is not valid or is not a project server.
Internet explorer is set to work offline. The server could not process your
request. An internal server error ocurred."

The link is valid and works from the internet. Also, because the domain is
different, the workspaces are not accessible. Is there a way to change the
web address while still maintaining the workspace and all the information is
holds?
 
J

Jackson T. Cole

Just to tbe clear, you did redefine your server account(s) in Project
Professional to reflect the new domain, right? A bit more user interface
detail might be needed to understand the parameters of the problem.

Regarding the workspaces (aka: SharePoint web sites), when a project is
saved, and automatic creation of sites is "on", the base URL for the new site
is the one found in the "Admin/Manage Windows SharePoint Services/Connect to
SharePoint Server" parameter:

"Create a site under this SharePoint URL: "

The new address is stored in the Project Server database, and only the
site-specific part can be changed, NOT the root. It would take a sit-down
with your DBA to change addresses created under ".mil" to something with
".com'.

Hope this helps ...

JC
 
C

Christie

Yes, the server account in Project Pro was redefined. If I open MS Project
Pro from my desktop, click tools - enterprise options - Microsoft Officer
Project Server User Accounts - add - then I enter my account name (using
windows authentication account info) and the project server URL (the new
one). When I click test connection I get the error mentioned below. We had to
change the domain name so that our customers still residing on the ".mil" can
still access project server.

Regarding the workspaces, we want to change the root and not the
site-specific part. We have a lot of information on the current workspaces.
We just want to move them to the new server. Is there a way to do this
without having to recreate all the information?
 
J

Jackson T. Cole

I don't understand the statement "We had to change the domain name so that
our customers still residing on the ".mil" can still access project server."

Whatever, if I understand the rest of your reply, the servers running MS
Project Server 2003, SQL Server, and WSS have moved to another domain
(".com), but there are still users in ".mil", right?

First, let me say that from my experience in my shop, as well as what I
read here and in "Project Server 2003 - Unleashed", Professional HAS to be
executed on a machine that is in the same domain as Project Server. That is
accomplished either by a hardware connection, VPN, or terminal server.
Professional even opens a DIRECT ODBC connection to SQL, and users have to be
recognized there by individual or domain group accounts. I think this
restriction is going to be eased in the next version, but for now, I don't
see how your ".mil" users are going to use Professional except by VPN to the
".com" domain, or setting up a server with lots of terminal server ports that
is in the same domain as Project Server, and installing Professional there.
Maybe Dale or Gary can provide another answer; I can't, sorry!

PWA is still usable, if your new Project Server domain is registered in
DNS, or if the IP address is a fixed address, not in a DHCP farm.

Now your SharePoint problem is a bit easier. If you have a registered
domain name or fixed IP address pointing to the WSS server, Sharepoint sites
sites are accessible from anywhere. Users just need to know the URL with the
domain name/IP address, and their domain login info. It would seem all you
did was change the registered domain name, not the "node" name of the server,
right?

As I explore the database tables, I may have erred in saying that a DBA
has to change table entries in Enterprise Manager. What is the entry in your
current Project server environment to:

"Create a site under this SharePoint URL: "

in the Administrative section? This would be how PWA would get to the
SharePoint sites from Project Center views. This appears to be a standalone
entry in a table, and thus changing the URL in Admin may allow for existing
sites to be found at the new location.

So, it appears we struck out with Professional, but PWA/sharePoint is
still salvagable. Let me know how you defined SharePoint URLs, and we go from
there.

Hope this helps ...

JC
 
C

Christie

We had to change from just prj1/projectserver to the entire domain name of
prj1.ourdomain.com/projectserver so that the external .mil users can access
the project server.

The .mil users are readers only. Only about 6 people are project managers
and have a need to connect MS Project Pro to Project Server. Those users are
on the .com domain. We only want the connection to Project Server from a MS
Project Pro computer on ourdomain.com

We are stumped because to type in the prj1.ourdomain.com/projectserver in
the address line of the internet works, but to type the same link into the
project server account inside MS Project Pro will not connect.
 
J

Jackson T. Cole

If ".mil" users are read-only, they can use PWA via the full domain URL
address. Professional in this version does NOT work outside the domain that
Project Server is in, period!

JC
 
C

Christie

You are confusing me. I have no ".mil" users that need to access MS Project
Pro!! The only reason I mentioned them is to explain why we had to change the
server name to use the entire domain in the address. The PMs that need to
open MS Project Pro from project server are all located on the new ".com"
domain.

Since my last post, we have made some progress and were able to get the
connectino from MS Project Pro to work. However, when you try to open MS
Project from the project server we still get the error that says you need MS
Project Pro 2003 in order to perform this action. But if I open MS Project
Pro, it opens online with the projectserver connection and if I file-open,
all the projects that are published to the projectserver appear and can be
opened and manipulated.
 
Top