Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nsrxchsv.exe errorcode 148

Status
Not open for further replies.

virag0640

Technical User
Sep 6, 2005
14
AU
Can anyone please help with this Legato MSEXCH setup?

I have a Client configured and just licensed for the
MSEXCH module. We added the nsrxchsv.exe to the
Backup Command Field and ensured the Legato Services
are running as the remote user "ex_service".

But the backup repeated fails with the error below.
Please note, I do not have access to the MS boxes - I am
a UNIX admin, but the Legato Client config appears to be
identical to 2 other servers configured the same way.

Please note the dump of info below. Any assistance
would be much appreciated:

# savegrp -vvvv -l full -c vail exchpf-daily
vail:MSEXCH:pF level=full
05/23/08 12:29:16 savegrp: Run up to 24 clients in parallel
05/23/08 12:29:16 savegrp: vail:probe started
savefs -s myserver -c vail -g exchpf-daily -p -l full -R -v -F MSEXCH:pF
05/23/08 12:29:28 savegrp: vail:probe succeeded.
rcmd vail, user root: `savefs -s myserver -c vail -g exchpf-daily -p -l full -R -v -F MSEXCH:pF'
nsrexec: authtype
type: NSR client description;
pools supported: Yes;
browse time supported: Yes;
multiple balanced streams supported: Yes;
remote user: ex_service;
groups: Domain Users, Everyone, IIS_WPG, Offer Remote Assistance Helpers, Users, Administrators, SERVICE, Authenticated Users, This Organization, UWS-gs-SOE-RemoteAdm
inGroup(test), Domain Admins, UWS-gs-RemoteAssistanceGroup, UWS-gs-ITD-Exchange Service Accounts, Remote Assistance, UWS Exchange Administrator, Offer Remote Assistance Helpers, $DUPLICATE-15273;
client OS type: Windows NT Server on Intel;
CPUs: 4;
kernel arch: INTEL_PENTIUM;
machine type: server;
MB used: 134134;
NetWorker version: 7.3.2.Build.364;
OS: Windows Server 2003 5.2;
version: 7.3.2.Build.364;
save set: path="MSEXCH:pF", arg="MSEXCH:pF", level=full, diskno=0, max_sessions=1,
stype=save ;
parallelism: 8
vail:MSEXCH:pF level=full, dn=0, mx=1, vers=ssbrowse, p=4
05/23/08 12:29:28 savegrp: vail:MSEXCH:pF started
nsrxchsv.exe -s myserver -g exchpf-daily -LL -f - -m vail -l full -W 78 -N MSEXCH:pF MSEXCH:pF
05/23/08 12:29:30 savegrp: command 'nsrxchsv.exe -s myserver -g exchpf-daily -LL -f
- -m vail -l full -W 78 -N MSEXCH:pF MSEXCH:pF ' for client vail exited with return code 148.
05/23/08 12:29:30 savegrp: vail:MSEXCH:pF succeeded.
* vail:MSEXCH:pF rcmd vail, user root: `nsrxchsv.exe -s myserver -g exchpf-daily -L
L -f - -m vail -l full -W 78 -N MSEXCH:pF MSEXCH:pF'
05/23/08 12:29:30 savegrp: vail:MSEXCH:pF will retry 1 more time(s)
05/23/08 12:29:30 savegrp: vail:MSEXCH:pF started
nsrxchsv.exe -s myserver -g exchpf-daily -LL -f - -m vail -l full -W 78 -N MSEXCH:p
F MSEXCH:pF
05/23/08 12:29:31 savegrp: command 'nsrxchsv.exe -s myserver -g exchpf-daily -LL -f
- -m vail -l full -W 78 -N MSEXCH:pF MSEXCH:pF ' for client vail exited with return code 148.
05/23/08 12:29:31 savegrp: vail:MSEXCH:pF succeeded.
* vail:MSEXCH:pF 1 retry attempted
* vail:MSEXCH:pF rcmd vail, user root: `nsrxchsv.exe -s myserver -g exchpf-daily -L
L -f - -m vail -l full -W 78 -N MSEXCH:pF MSEXCH:pF'
05/23/08 12:29:31 savegrp: vail:MSEXCH:pF will retry 0 more time(s)


Thanks very much


rachel
 
I assume that the return code is nothing else but the Windows return code/error number. In this case it resolves as follows:

C:\>net helpmsg 14

The path specified cannot be used at this time.


C:\>


The MS solution for this problem is just to retry the operation at a later time. But it could also be that you must restart the server.
 
Hello Rachel,
MSSXCH:pF is the saveset for Public folders.
Are there any public folders on this exchange Server ?
If thr answer is yes check the access rights to the public folders or let the exchange admin check the rights.
 
Hi everyone,
thanks for the advice. We ended up resolving it.

I made a checklist for the Exchange admin to go through
and when we got to "Module Version" we discovered
he had somehow installed a very old exchange Module
2.0 on the 2003 version server.

Updating this to 5.1 resolved the issue immediately!


Thanks for all your help!


rachel
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top