I recently upgraded our GroupWise system to 7.0.3 from version
7.0.2HP. The MTA, POA, and GWIA upgraded successfully. I was UNABLE to
upgrade WebAccess. After multiple attempts, I decided to rename the
WEBAC70A folder, delete the eDir object and install fresh. Again, it
failed to install. After every attempt it always proceeded to the
point where it was supposed to start copying the files, but it never
did, even after waiting anywhere from 10 to 30 minutes. I know Novell
says it is ok to run an older version of the WebAccess agent, which I
am running now. But I DO like to have ALL modules at the same patch
level. Any help would be greatly appreciated.

Thank You

Hi there,

I would like to put a groupwise login box on my company web site front
page, not just a html link to "/gw/webacc"

I tried copy and pasting the login but it doesn't work as expected.

Can anyone advise?

Thanks,

I have several user accounts ( my own account included) that will
not load the Frequents Contact address book when logged into
GroupWise Web Access. The address books appear blank in web access
but populated when checked via the GW client.

I do not think it is an issue with the web browsers, I have
recreated the issue on several machines, running IE 6, IE 7 and
Firefox. Another user can log onto the same machine, and view FQ with
no problem, so I also believe this rules out network speed.

So far it is an issue with a handful of 800 users, but I am fighting
a battle to switch to Outlook, and I really don't need another black
eye with GroupWise right now.

Is there something else I should be looking for?

Jim

Hi,

A small problem with 7.0.2 when users chose [Save as] then select
[Open] from the IE dialog box word opens OK, but they puts the
following error dialog up:

"This file could not be found
Try one or more of the foloowing:
*Check the spelling of the name of the document.
*Try a different file name.
(c:\.............whatever%%20its%%20called.doc)

Selecting [Save as] then [Save as] works fine, just not when they try
to open the attachment.

We are using the WebAccess application on SLES 9.1 with a seperate
agent on Netware 6.5.

Strangely a second application with broadly the same config works OK.
My gut feeling is its something in the Apache config, but cant see it.

Oh and by the way we aren't using SSL for this site - I'm aware of the
issues with SSL/GroupWise/Caching/Attachments......

ANy help gratefully received...

Thanks

Hello - I have a user who has her Mailbox system folder missing in Web
Access. When she logs into Web Access, incoming emails are displayed,
but under her NAME, rather than under the Mailbox folder heading. Once
she clicks any other folder, she cannot get her incoming mail to view
without logging back in and out. The actual folder and icon is
missing. GW 7.0.2 HP1 did NOT fix the issue.......... Thanks

I've been dealing with a problem with our Groupwise email server for
quite some time now that only affects the web access. Were running
Groupwise 7.0.1 with the Interm patch installed on a SLES9.
Occasionally the web access with go down and display a page that says
"Internal Service Error". We can not consistently replicate the error,
but can usually cause it to occur after a few repeated trys (usually
involving updating of cabinet or calender). I then log into the server
and restart the groupwise web access and tomcat services and it works
fine for again for a while.

I've found some interesting logs that detail what exactly is happening
at the time of the crash. There must be some issue going on between
Java and Tomcat that causes this to occur. I wont post the full log
detailing the error unless requested as they are huge, but I will post
what I believe are some of the important key parts. Here is what I've
pulled up so far:

from /var/opt/novell/tomcat4/logs/catalina.out :

Hi,

I was talking with our PSE about this subject. He slipped me the NDK
which covers this. However I think this NDK covers 5 and 7 as changes
made in the customization.properties file as suggested did not effect
the page in question. I even restarted the entire server even though I
knew this was not needed.

Path I used was sys:tomcat\4\webapps\gw\web-inf\classes\com\novell
\webaccess\templates
File: Customization.properties

The PSE also, after trying, stated he received the same results.

Is there a definitive on how to do this for GW7 web access? If it
matters we are running, I believe, SP2. I did this on prior versions
but am running into a brick wall on this version.

Thank you,

Brian

GroupWise Web Access Agent 7.0.1 on Netware 6.5SP6. It loads
fine and says that it's ready for work, but when one tries to see
it over the web, the web page returned says that there is a
problem with the website.

I've unloaded, reloaded, and restarted the server. In my list of
services at the console, it says Apache 2.0.59 is there, but when
I go to the screen all I have is .
When I do that, the service apparently closes.

Wondering what to do from here.

I am having a weird problem. I have an account that cannot login
through Web Access. When I enter the userid and password it just
flashes the screen, blanks the password, and that is it. No login, no
error message, nothing. The WebAccess agent log shows that the user
was logged in and then about a min later it says "Conversation timed
out". The apache access log and error log show nothing. The POA log
shows that the account was logged into via WebAccess. I know it is
just this account because I can login to a different account on the
same machine. I have run the following utilities on the account with
no success:
- reset user options
- structural rebuild
- analyze-fix (with contents)

My system info is:
- GW WebAccess Agent 7.0.2
- Novell Netware 6.5.5

I am stumped on this one. Does anyone have an idea what is going or
other things I can look at to get more information?

-Chris H

On Jul 5, 5:43 pm, hquiller gmail.com> wrote:

Can you try using both Firefox and IE to test? I'd like to eliminate
a browser setting of some kind as the culprit.

Also, have a user that is working successfully try logging into a
workstation for someone that doesn't. That way we can eliminate a
workstation setting as the problem, and really target the server.

I currently have a two WebAccess 7.0.2 servers working flawlessly
(one in production, one in test), so the code for SP2 seems to be
solid.