Re: Serious Bug using Office 2000 with Project Server 2003 and WSS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David Blair (david_at_3blairs.com)
Date: 02/09/04 

Date: Mon, 9 Feb 2004 14:57:41 -0800

Gary,

More info... I think I found what is going on, but I do not know what is
causing it. Everything that is happening is local and I believe in the
registry. When I go through the steps to cause the problem there is an
entry in the registry that somehow does not know who I am logged in as
anymore. In fact, even if I 'Cancel' the Username dialog a few times, the
PWA web page eventually shows. Here is the location of the entry:

[HKEY_USERS\S-1-5-21-3865435737-3326842981-867535038-1005\Software\Microsoft
\Office\11.0\Common\Internet\Server Cache]

I'm not a registry guy, but if I deleted the entry below this one that
refers to my Server name, log out and back in, things work fine. Just don't
touch the Discuss button.

David

"Gary L. Chefetz [MVP]" <garyNOSPAM@chefetzDOTorg> wrote in message
news:%232J8Lw07DHA.3880@tk2msftngp13.phx.gbl...
> David:
>
> You'll find significant functionality reduction using Office 2000 with
> Project Server 2003 and WSS. The new Office version is the first (IMO) in
a
> long time to offer a compelling upgrade story and well worth a look. You
can
> disable discussions and these are not enabled by default. You do not need
to
> enable version control either.
>
> If you can give me a step-by-step write up on reproducing the problem and
a
> description of the desktop environment on which this happens, I can submit
> it to the quality team for review.
>
> --
>
> Gary Chefetz [MVP]
> http://www.msprojectexperts.com
> We wrote the book on Project Server
>
>
> "David Blair" <david@3blairs.com> wrote in message
> news:OT4TKQz7DHA.1112@tk2msftngp13.phx.gbl...
> > Please help. We are using Office 2000 and have installed Project Server
> > 2003 with WSS on a Windows 2003 server. All is fine except we cannot
edit
> > documents with Word 2000 that were uploaded to WSS. Worse (and a show
> > stopper) is that if we try either the 'Check Out' or 'Discuss' feature
> from
> > the Documents page, the users Office Profile gets corrupted and each web
> > page from then on requests a Windows logon (because Windows doesn't know
> who
> > you are anymore). Company policy states that 3 unsuccessful logons
> > deactivates the user.
> >
> > Any way to remove those commands or anyone have a solution? (Besides
> > upgrading everyone in the company to Office 2003)
> >
> > Thanks,
> >
> > David
> >
> >
>
>

Relevant Pages

  • Re: Specified path does not contain any applicable device INFs
    ... Go to the following registry ... The value shoud be %SystemRoot%\Inf and of type REG_EXPAND_SZ. ... David wrote: ...
    (microsoft.public.win2000.setup)
  • Re: event ID29 time provider not available
    ... Hello David, ... Microsoft Partner Online Support ... |> This issue may occur if the Network Load Balancing service is referenced ... Locate and then click the following registry subkey: ...
    (microsoft.public.windows.server.general)
  • Re: Registry question
    ... RegMaid.exe Helps Clean Up the Registry ... Microsoft Visual C++, 32-bit Learning Edition, version 6.0 ... RegMaid provides information about entries that are believed to be ... server file entry cannot be found by the system. ...
    (microsoft.public.windowsxp.general)
  • Re: MS Backup
    ... Okay, I had to go to bed too:) Now, no cd is nothing to worry about. ... reason you don't have that entry in your registry is because you don't have ... >> msnewsgroups..on the right, then go to the toolbar, click on view>current ...
    (microsoft.public.windowsxp.basics)
  • Re: Word opens slowly
    ... See http://support.microsoft.com/?kbid=329820 "How to use Office programs with the Norton AntiVirus Office plug-in" for more information. ... I have done three fresh install, scanning first, then defragging, then cleaning the registry before reinstalling Office. ... HKEY_CLASSES_ROOT\word\10.0 Delete the entire 10.0 entry. ...
    (microsoft.public.word.application.errors)