Sharepoint services error

[elgreenfield]

Getting this error when trying to go either into risks or issues within
PWA

The documents, risks and issues features in Project Web Access use
Windows SharePoint Services.
There is a problem establishing a connection with the Web server
running Windows SharePoint Services. Contact your system administrator.

 

[Kevin W Flanagan]

Here are a few of the options that come to mind regrading this error:

- Another application may have changed the Proxy Configuration (proxycfg)
values. You will need to rerun the Proxy Configuration utility.

- The account may have had the password expire. These accounts used for
setup should be set for passwords to never expire.

- If another application has been installed, there could be a port conflict

- The PSComm+ service was stopped or disabled. Rerun PSComm+ utility.

- Even something as simple as running an iisreset or rebooting the server
may fix this

- Also, try to directly navigate to the WSS web space; if you can enter,
then only the relation between Project Server and WSS was broken; if you
can't enter, then the problem is with WSS.

-You might need to reinstall WSS or rerun the WSS configuration wizard from
the Project Server installation disc

Without further information it is kind of hard to nail this down to the
specific fix.

Kevin

 

[Rolly Perreaux]

Hi elgreenfield,

A couple of questions...

1. Were you able to successfully access Project Risks and/or Issues
prior to the error?

2. Are both Project Server and SharePoint on the same server?
If so, do they have their own web sites? For example:

Project Web Access = http://<servername> (default on Port 80)
SharePoint = http://<servernameort number> (anything except Port 80)

3. Can you access the Project Server Public Documents site?
http://<servernameort number>/sites/MS_ProjectServer_PublicDocuments

4. Can you access the SharePoint Central Admin site?

5. Can you provide any additional infrastructure information so that we
can help you.

Let us know when you have chance

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Hi Kevin,

What is the PSComm+ Service and where can I find it on the Project
Server?

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

The PSCOM+ is left over from 2002 days. But it is found:
installdrive:\Program Files\Microsoft Project Server\Bin\1033\PSCOMPlus.exe
(COM+)

 

[Rolly Perreaux]

I know what the PSComPlus utility is.

But you said "The PSComm+ service was stopped or disabled."
I've never heard of the PSComm+ service.

So what is that and where can I restart it?

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Don't worry about it Kevin
I googled "PSComm+ service" and I found this old post on the MCSE
Braindumps web site
http://www.mcse.ms/archive184-2004-7-886418.html

BTW, that post is wrong too.
There is no such thing as a PSComm+ service for Project Server 2003

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

I know what the PSComPlus utility is.

But you said "The PSComm+ service was stopped or disabled."
I've never heard of the PSComm+ service.

So what is that and where can I restart it?

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

There are "hiccups" that happen that cause the COM+ utility settings to stop
working. It is not uncommon to have to rerun the utility to get the
"service" running again. It runs in the background and is a subset of the
COM+ services on Windows servers. Mostly access programmaticaly, thus the
utility.

 

[Rolly Perreaux]

Hi elgreenfield,

I managed to recreate your error and the steps on how to fix it:

1. From the Project Server, click Start --> Run
Type CMD and click OK.

3. At the command line and type the following command:
PROXYCFG.exe
This command displays the current settings
Also write down the settings as you may need them (just in case)

4. Then type the following command:
PROXYCFG.exe -d
This command will clear the settings

5. Then type the following command:
net stop wuauserv
This command will stop the Automated Updates services

6. Then type the following command:
net start wuauserv
This command will start the Automated Updates services

7. Then type the following command:
PROXYCFG.exe -d -p <URL of project server> <bypass-list>

The bypass list will include the computer name and fully qualified
domain name of the Project Server

If you have multiple proxy server names (which you should) use double
quotes and semicolon to separate the servernames. For example on my
server I typed:
PROXYCFG.exe -d -p "https://PSDEMO;http://PSDEMO"
"<local>;psdemo;psdemo.adatum.com;*.microsoft.com"

NOTE: command is all on one continuous line and there must be a space
between [-p <server-name> [<bypass-list>]
For example: ...http://PSDEMO" "<local>;...

And I also added *.microsoft.com to the bypass list so that I wouldn't
create problems accessing the Microsoft Update website to get the latest
server and application updates.

8. From PWA, click on a link to the SharePoint Project Workplace site to
see if you can access.

Let us know if this works...

PS
For anyone wanting to recreate the error, after Step 4 check if you can
connect to your SharePoint Project Workplace site. You should not and
also get the following message:

"The documents, risks and issues features in Project Web Access use
Windows SharePoint Services.
There is a problem establishing a connection with the Web server running
Windows SharePoint Services. Contact your system administrator"

Then continue with the remaining steps and you should get access again

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Actually that's not true

The PSComPlus utility creates the COM+ applications that interface
between Project Server and Analysis Services (OLAP) and Project Server
and Windows SharePoint Services. The PSComPlus utility has nothing to do
with a Windows Server service, it's merely a tool to facilitate creating
the COM+ applications that were originally created during the Project
Server 2003 setup.

Here's a quick PSComPlus Utility/COM+ Applications lab to prove the
point:
NOTE: You must know the name and password for the OLAP services account
and WSS services account prior to starting the lab and PLEASE DO NOT
complete this lab on a production server!

1. From the Project Server, click Start --> Programs --> Administrative
Tools --> Component Services
2. At the Component Services console, expand to Component Services -->
Computers --> My Computer --> COM+ Applications. This will display the
following applications:
Microsoft Office Project Server OLAP Cube Component
Microsoft Office Project Server WSS Admin Component
3. Minimize the Component Services console.
4. Open Windows Explorer and navigate to the following directory:
C:\Program Files\Microsoft Office Project Server 2003\BIN\1033
and run PSCOMPlus.exe
5. In the Microsoft Office Project Server COM+ Settings application,
verify that "Process this identity update" is selected for both services
and click "Delete All COM+ Apps".
6. Maximize the Component Services console and press F5 to refresh.
Notice the Project Server COM+ Applications have been removed.
7. Minimize the Component Services console.
8. From Windows Explorer, run PSCOMPlus.exe again.
9. In the Microsoft Office Project Server COM+ Settings application,
verify that "Process this identity update" is selected and type the
Username* and Password for each service and click "Create/Update COM+
Apps".

*NOTE: Username must be in the format of <DomainName\UserName> or
<ComputerName\UserName>

10. Maximize the Component Services console and press F5 to refresh.
Notice the Project Server COM+ Applications have been recreated.
11. Right click Microsoft Office Project Server WSS Admin Component and
click Properties.
12. In the Microsoft...WSS Admin Component Properties dialog box, click
Identity tab and verify the Username is the same that was typed in the
PSComPlus Utility.
13. Complete Steps 11-12 for the Microsoft Office Project Server OLAP
Cube Component.
14. Close the Component Services console.

So, the PSComPlus utility IS NOT a background subset service of COM+
services, but a tool to facilitate creating the COM+ applications for
Project Server 2003.

For more information on COM+ Administration, please review the following
Microsoft TechNet article:
COM+ Administration: Understanding the Component Services Administrative
Tool
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologie
s/iis/deploy/depovg/compl.mspx
OR
http://tinyurl.com/z7s6z

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

Maybe I do not express it well, but this is traight off of Micorosft's
officla COM web site : "Microsoft COM (Component Object Model) technology in
the Microsoft Windows-family of Operating Systems enables software components
to communicate. COM is used by developers to create re-usable software
components, link components together to build applications, and take
advantage of Windows services."

 

[Rolly Perreaux]

Kevin, you're missing the REAL point here. You said in your original
reply, "The PSComm+ service was stopped or disabled."

There is no such thing as a PSComm+ service or as a sub-service to COM+
System Application service. Period.

The PSComPlus utility was created in order to facilitate re-configuring
the COM+ applications that are originally created during Project Server
2003 Setup. Have you tried my lab, it totally reinforces the entire
concept of the utility.

OBTW, your comment about PSComPlus "is left over from 2002 day" is also
incorrect. If you check the file properties of PSComPlus.exe you will
note that the version number is not the same as the version in Project
Server 2002.

The problem is that you cut n pasted a reply from the MCSE Braindump
forum that "kinda looked like a right answer" but you didn't check if it
was technically right, when it was _absolutely_ wrong.

So next time, when people have a technical question, don't just Google
and cut n paste without verifying or understanding the technology. There
are just too many people that need assistance in helping them with their
serious technical problems and would like to get good information to see
if they can fix it before having to call Microsoft PSS Support.

That's the whole purpose of these newsgroups.

I'm really sorry if this reply sounds harsh, but I've heard too many
stories from students that have been given information that sounded good
at first, but got burned in the process. The problem is they usually
have to put in a lot of extra hours just to make the software work
because they took some bad advice.

It's just my Hot Button issue, nothing personal.

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

Rolly-

I think your replies speak volumes about you and your lack of respect to
others on this newsgroup.

 

[Rolly Perreaux]

Kevin, first allow me to apologize for the tone of my previous post. I
see now the tone that was conveyed within the message and the undeniable
fact that it appears to be a personal attack upon yourself. My intent
was not to attack you personally, rather than to raise concerns with the
information you were putting out to the query that started this thread.

My point merely is, that as community, we provide advice to the many
thousands of members, we have a responsibility to exercise due diligence
and ensure that we are in fact providing good and sound advice and
solutions to those seeking help. Part of that responsibility, in my
view, is that we must ensure the technical accuracy of information we
gather from other newsgroups, blogs or technology forums scattered
around the Internet. Certainly, there are many excellent resources
available to assist us in finding the answers to others' problems and I
support and encourage the use of those resources. We just have to make
sure that the information we are gathering is correct.

Project Server and SharePoint technologies are my areas of technical
expertise and I could see right away that the information provided in
the post from which you drew your response from was incorrect. I
applaud your efforts in attempting to find a solution to a problem
presented, however, it is a dangerous practice to assume that everyone
who posts information is also well versed and experienced with the
intricacies of the technology in question.

The last thing we want to do is lead someone down a path that will
either not solve the problem or inadvertently create new or additional
problems.

Again, my apologies for the tone of my previous post.

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

Thanks
--
Kevin W Flanagan, PMP
EPM Consultant

Kevin, first allow me to apologize for the tone of my previous post. I
see now the tone that was conveyed within the message and the undeniable
fact that it appears to be a personal attack upon yourself. My intent
was not to attack you personally, rather than to raise concerns with the
information you were putting out to the query that started this thread.

My point merely is, that as community, we provide advice to the many
thousands of members, we have a responsibility to exercise due diligence
and ensure that we are in fact providing good and sound advice and
solutions to those seeking help. Part of that responsibility, in my
view, is that we must ensure the technical accuracy of information we
gather from other newsgroups, blogs or technology forums scattered
around the Internet. Certainly, there are many excellent resources
available to assist us in finding the answers to others' problems and I
support and encourage the use of those resources. We just have to make
sure that the information we are gathering is correct.

Project Server and SharePoint technologies are my areas of technical
expertise and I could see right away that the information provided in
the post from which you drew your response from was incorrect. I
applaud your efforts in attempting to find a solution to a problem
presented, however, it is a dangerous practice to assume that everyone
who posts information is also well versed and experienced with the
intricacies of the technology in question.

The last thing we want to do is lead someone down a path that will
either not solve the problem or inadvertently create new or additional
problems.

Again, my apologies for the tone of my previous post.

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com