Link to home
Start Free TrialLog in
Avatar of cendrizzi
cendrizzi

asked on

Another user inbox restore problem

We've been running Groupwise for some time and believe it or not, I just barely got the need to restore some emails for a user (careful users I guess).  

So for the first time I find myself settting up this capability and feel I'm 90% there.  My problem is very similar to this one but unfortunatley does not work for me: https://www.experts-exchange.com/questions/21586064/GroupWise-Restore-Users-Inbox-Problems.html

Basically I keep getting the error:
[Groupwise Error 8209] The path to the file is invalid or the file does not exist.  Specify a valid path and file name.

Here is what my post office log file says:
13:07:10 295 The database facility reported error [8209] on ngwguard.db
13:07:10 295 Error: Path not found [8209] User:cendrizzi

For my restoare I simply don't have the space on my email server so I have my po restored on another server.  As I understand the POA needs access to this server since when the user clicks restore it's the POA that grabs the file the user specifies to restore (I'm guessing just viewing it is taken care of by the client).  Given this I'm guessing the problem is a permission issue but I'm having a hard time resolving it.  First of all is that we currently have eDirecotry and AD.  All windows machines use AD and this machine I'm restoring to is no exception (we have the two directory services syncing although this isn't perfect and needs to be standardized better).  The machine that I restored to, however, does have the Novell client installed and can access all resources on the email side of things.  So on the POA agent settings I put in the remote username and password as administrator (at least for now) but apparently it can't get to the stuff, even though I've gone as far as giving the special group "Everyone" full control permissions to this restore directory (Shared permissions are the same).  Furthermore, I made sure the shared file is less than 8 char even though this is a GW 7 machine and I don't think it applies or matters anymore.

So am I on the right track?  Any pointers on troubleshooting the issue?  I think I may have reached my limit as I'm not a GW troubleshooting guru (never really had to be since GW has been very stable).

Thanks very much in advance!
Avatar of ShineOn
ShineOn
Flag of United States of America image

What is the GroupWise version/SP you're running?
Avatar of cendrizzi
cendrizzi

ASKER

Thanks for the reply.  It's 7.0, no service pack (they don't have one out do they?)
Almost, any day now (it's in open beta).
Ok, I remember they said they would release it around brainshare.   I've noticed that 7 isn't quite as stable so I'll be very happy for the SP.

Any thoughts on my issue?  I'm very much a linux guy and on Linux I would log on under the POA account and try to connect to the share until it works.  With Netware I don't know as much.   I gave the username and password of the administrator, so if I was connecting from a windows box it would work.  I thought about changing it from the restore servers name (in the restore path) to an IP address, avoiding any DNS complications.  When connecting to a windows machine, especially one that uses AD in addition to have the client, do I need to use the DOMAIN\username syntax?  With the novell client on this server should it not be able to connect seamlessly to this share from the GW server?

I just don't understand why it's not connecting...

I think you do need DOMAIN\username syntax, since it's windoze filesystem/share permissions we're talking about and not NetWare filesystem trustee rights.

Speaking of filesystem/share permissions - did you make sure that both the NTFS permissions and the share permissions were set so the POA and the user both can access the restore folders?  
Yes, both are given full control.  I'll try the domain syntax.

Thanks!
The question is whether that is a very generic error or if it is specifically a path problem.  I wonder why the path would not be working if that is a case.  With the Netware client should it not be able to talk to it just like it's another netware computer?
Not really, because it's not a NetWare computer.  It's a Windows computer. The Novell client just lets you use Novell products, like eDirectory.  It won't redirect to Windows resources - it leaves that for the Windows client to do...

It's a generic error (8209) that means the file/folder can't be accessed for some reason.  If it's not a permissions problem, then it's a path syntax/access problem, or vice-versa.  Or both.  

I say syntax/access because it could happen if the network link were broken somehow, too - like if they were on 2 separate subnets without a bridge or route between them, or the switch died, or some such...  Can't be found is can't be found.

Since you're talking windows-to-windows you have to use windows networking transport, functions and syntax, as well as authentication.  If it were two NetWare boxes it'd be different (and probably easier.)
Is it windows to widnows though?  I mean I can view the files well, which I'm assuming is the client connecting fine.  But when I try to do a restore I get the problem.  Which is when the POA is trying to access the file.  THerefore would it not be a Netware to WIndows problem?
I have about 8 gigs of space left on the email server.  If I could restore just the two users who need some files then that would work but I'm not sure how to do that.  Each user has an associated id number.  If I could get that number could I not just restore those files that are associated with those users and have it work?  That way I would not have to restore the 40+ gigs of information....

Any chance of doing this?  I mean it's kind of crazy that I would have to restore all that data every time I want to restore a couple of emails.  Isn't there any other way?
ASKER CERTIFIED SOLUTION
Avatar of ShineOn
ShineOn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial