Project Server Security Logon/McAfee ScriptScan Disabled - Problem

D

Dan

I have read the other posts on this issue, but disabling ScriptScan in McAfee
8.0 does not prevent the problem/annoyance from occuring.

When first logging onto the Project Server with Project Pro the process gets
stuck on the Project Server Security Logon dialog. After cancelling out and
retrying, login works fine.

I know it is just an annoyance, but our Sr. Mgt. has found a lot of these
minor issues and keeps looking for resolution. Any news or workarounds on
this one???
 
S

Scott

Dan - We have the same issue here. As a matter of fact I was was of the few
who did not have to login twice but within the last week something changed
and now I have to login two times to get connected. I'd like an answer to
this as well.
 
S

Scott

Dan - Scott again - Just read another post and the light bulb went off! The
'What changed' that I was referring to was my upgrade to McAfee 8.0! No
solution, just a root cause.
 
D

Dan

Yes, the problem is with McAfee 8.0. If you disable the app, no problems -
no solution there. Some have reported success disabling the ScriptScan
feature. This worked for a while here, but stopped working several weeks ago
(in some update of McAfee??).

--
Dan Beebe
Manager, Technology & Development
Vision2Reality
 
D

Dan

We contacted McAfee and recieved this answer:

Solution1:
There are currently two workarounds in place for this issue:

1) Unregister Script Scan's loaded module, ScriptProxy.Dll, will
prevent the failure from occurring. If you installed VirusScan to the
default install path you can run the following from a CMD/Run Prompt:

regsvr32 /u "C:\Program Files\Network
Associates\VirusScan\scriptproxy.dll"
 
S

Scott

Dan,

Thanks! This solution did the trick. I had an error when I first ran the
command and had to modify how I ran it. It's probably my lack of command
language knowledge. I did it this way:
1. From CMD Prompt: c:\>cd program files\network associates\virusscan
2. From CMD Prompt: c:\program files\network associates\virusscan> regsvr32
/u scriptproxy.dll

I assume because you talked to McAfee this fix doesn't effect McAfee's
performance. Do you know for sure?

Thanks again
 
D

Dan

Scott,

I didn't post the "We contacted McAfee..." post. Someone else has/created
an account with a screen-name of Dan. Use posted solution with caution.

--
Dan Beebe
Manager, Technology & Development
Vision2Reality
 
S

Scott

Dan,

The solution is listed on McAfee's knowledgebase site under solution ID
kb41346 dated 25JULY2005.

Scott
 
J

John Cello

Unregistering the .dll is indeed McAfee's "fix". Sadly, even as a kluge fix,
its only temporary. I've got a client site that is currently suffering this,
and after unregistering the .dll, the problem resurfaces again in a few days.
(The client IT department is speculating that when the anti-virus software
self-updates, it "fixes the fix")

They have resorted to adding a desktop icon that runs a batch file
unregistering the .dll and then launches project. Unfortunately, this doesn't
work when opening a project from PWA.

And yes, by unregistering the .dll, you are losing protection from certain
malicious scripts.

Just as a poll, my opinion is that mcAfee needs to take ownersip of this
problem, as their software update broke a stable platform. Your thoughts?
 
R

Raj

Has anyone had anymore luck with this ?

Microsoft have tentatively released a hotfix
http://support.microsoft.com/kb/899341/en-us

But in our case it doesn't work - I've also uninstalled McAfee & ePolicy,
disabled the firewall and set browser zone security to 'Low'

Still no luck.

Annoyingly installing Project Pro 2k3 on a server works fine - eg its
definitely not a configuration thing but a desktop policy issue.

More annoyingly there is a distinct lack of transparency when
troubleshooting - filemon, regmon and procmon don't point to where the
problem lies.
 
R

Raj

Came up with a couple of fixes -

It seems something in our desktop build screws with a dll (most probably
something related to IE6SP2) required to authenticate.

Fixing the hanging login problem can be fixed (if the scriptscan thing
doesn't help) by

1. Fixing IE6 - either reinstalling or running the iefix tool
2. Jump to IE7
3. Setting a server side policy - 'Impersonate a client after
authentication' and adding in the domain account used to run the Project
Server
 
A

ad9aggie

The fix for this is twofold:

Install Project Pro SP2 on all client boxes and Project Server SP2a on all
servers. Then install the Project Pro/Server SP2 Rollup on all client boxes
and servers.

The key is having the SP and Rollup on both sides of the installation.

Hope this helps,
 
M

Mocha

Hai My name is Yogi,
I've got the problem to. I couldn't login to Ms Project Profesional 2007
when i use diffrent login. In my company , each client computer login using
domain login. I tried to login to Project Profesional 2007 using my own
domain login and work but when i try to login using my friends login and it
always failed vice versa when i login to project profesional using my
friend's computer client.
for another information.Im using symantec antivirus.
Is Ms Project Profesional 2007 sp 2 has been released? How could i get it?
Thank you before and after...
:)
 
Top