• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

Invalid Checked In/Out Error: E511

GW6.0SP4 and NW6.0SP5, Clustered GW Environment and home drive.
Windows XP and W2K3 Terminal Services.

1.  User logs into the computer for the day.  GW starts up automatically.
2.  User uses GW to open a file from the Library for editing in Word Perfect 11SP3.
3.  User makes changes, some big some small in short time period or long time period and saves regularlly.
4.  Error:  WHen user tries to close the file GW Reports an E511 Error "Unable to reset document status".  This error indicates that the file is not checked out and therefore, the document cannot be saved back into the library.
5.  When the user, any user at this point, retrieves the document, the edits are not in the document.
6.  The file that WP worked on, Xnnnnn-1.wpd, still resides in the Check In Directory (H: Drive - off cluster server).

Can anybody think of why the file checked out in step two is reporting that it is not checked out in step 4?  Nobody else would be working on the documents at this time and nobody would intentionally reset the document status prior to the actual user would finishing their editing.

Any help would be appreciated.  

Thanks,

MB
0
MMDCisco
Asked:
MMDCisco
  • 7
  • 5
1 Solution
 
PsiCopCommented:
Interesting.

I hope you are aware that both GroupWise v6.0 and NetWare v6.0 are obsolete versions and have been EOLed. Latest GroupWise is v7.0, and NetWare has been replaced by Open Enterprise Server, which gives you a choice of a NetWare or Linux kernel.

Are users logging into the Windoze/TermServ environment with a common user ID, or does everyone get their own Windoze login?
0
 
MMDCiscoAuthor Commented:
I'm fully aware and I'm making the change by the end of the year.  Though they are EOLed, the programs should still be functional.  

The users are using their own login.

My biggest apprehensions about upgrading are uncertainties about the Cluster environments and the upgrade.  In addition, I don't have a lot of help down here as NW consultants are sparce in Texas.  I'm going to practice in a sandbox but the budget is tight so I am trying to replicate the environment in VMWARE's ESX Server.  Jumping to OES/Linux and GW7 is going to be a leap of faith unless I get the education first.  So, I'm working on it.

That said, I've tried using the latest SP by Corel for WP11 (WPX3 doesn't make a big change to that functionality) that was supposed to address this issue but with Hummingbird.  

If you've done an upgrade from NW6 to OES, with Cluster Services, I'd love to hear about it.
0
 
PsiCopCommented:
Note that's its nt necessary to "jump" to OES and GroupWise v7. Perfectly acceptable to move to NetWare v6.5 and GroupWise v6.5 as a migration path. And actually, OES-NetWare is NetWare v6.5 for the purposes you're considering. No need to switch to the Linux kernel at the same time.

I want to be clear about the login - you're using DLU or some other functionality to ensure each user has their own login IN WINDOZE. That is, they run the TermServ client, and connect in, ad when they login to eDirectory they are also logging in to Windoze with the SAME USER ID. Right? I just want to be very sure of that.

The GroupWise POA - its operating in Client/Server Mode, the POA Security setting is "High with eDirectory", right?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
PsiCopCommented:
Correcting a typo -->  Note that's its not necessary to "jump" to OES and GroupWise v7.

And yes, NetWare v6.0 and GroupWise v6.0 should be, as you say, fully functional. Heck, there are still places running NetWare v3.2 or even older. Just wanted to make sure you understood the status of the products.
0
 
PsiCopCommented:
Does it make any difference if the user checks out a document and then immediately checks it back in?
0
 
MMDCiscoAuthor Commented:
You're right, I don't have to 'jump' to OES and GW7 but I don't want to spend the next few years constantly upgrading to a new platform.  

The Terminal Servers are member servers of Active Directory and the computers (outside of TS) are also members of the same directory.  Each user has their own ID in AD and NW.

The POA is C/S mode but I don't know the answer for the security setting.   This is an intermitent problem and difficult to reproduce.  Actually, I have a way to produce it:  make a high powered attorney work under a deadline for another high powered owner then make shorten the amount of time the first attorney has to work by a factor of 3 thus making her rough draft the final draft.  Boom, changes won't make it in.  But if she has all week to do the work then everything will be just fine.

I'm starting a new question to address some concerns with the upgrade.  I wanna get this out of the way.

MB
0
 
PsiCopCommented:
Interesting that it is intermittent. I'm wondering if this is a communications issue. Are you able to correlate the errors seen by the user to any error messages on the POA?
0
 
MMDCiscoAuthor Commented:
Unfortunately, no.  There are no errors on the POA.  The question about communications has been brought up a few times.  Keep in mind that it's a terminal server with 15 users doing approximately the same tasks and only now and then do they have the issue.  Client32, latest service pack.  
0
 
PsiCopCommented:
Hmpf. Are there any people not using the TermServ environment for similar tasks? Are you able to isolate this problem to the TermServ environment, or does it happen with people not using the TermServ?
0
 
MMDCiscoAuthor Commented:
In the last six months, 10 people have been moved from the Terminal Server environment to local desktop computing.  There have been less than five reports of this occurring in that time.  These users can perform editing operations on up to 50 documents a day.  THose who have had the problem also reported other anomolies just prior to closing the document such as GW suddenly being brought to the front or they accidently closed a program or something else.    So, it's tough to say that the situations are identical but I think that it has happened on Windows XP along with Terminal Server.  Next week, the users that have the problem frequently on TS are moving to local desktop computing.

MB
0
 
PsiCopCommented:
Well, I know we've chewed this fat before, but I'm compelled to point out that GroupWise v6.0 predates both XP and W2K3. And Redmond is renown for deliberately breaking backwards compatibility with any products they perceive as competition. You have the last patch, yes, but the core code is from the 2001/2002 timeframe.

If your intent is to bring your GroupWise environment up to more modern code, I'd put more effort into that.
0
 
MMDCiscoAuthor Commented:
I've awarded the points because I believe that the solution is to change to the upgraded version of all involved systems then addressing the issues with the vendors themselves.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now