Client 7.1.0.4

[Dirk_Mueller]

Hi,

our envirenment:

NBU 7.1.0.4 - windows 2003 R2-Server

I have now updated the first windows-client to NB 7.1.0.4. In the policy is "All local drives". However, for a schedule we have some drives completely excluded, for example, D: \, E: \, etc.
Now we get for the jobs of excludet drives a error 90. With the old client we got status 0 and 0 kb.

Is this the new design, or do I have to change something, so I do not get any error messages?

Kind regards

Dirk

[Andy_Welburn · Accepted solution]

This certainly *was* an issue - but not sure at what point it got fixed:

https://www-secure.symantec.com/connect/forums/status-code-90-excluded-drives

http://www.symantec.com/business/support/index?page=content&id=TECH125205

Potential workarounds - removing multistreams or amend exclude list to D:\* etc

[RamNagalla]

hi,

could you check if this client has any exlude list in place..

you can check that form -- GUI---> host porperties---> clients --> properties

and also show us the failed job detaild status. 

and policy details

bppllist <policyname> -L

[Marianne]

Yes! Known issue!

You need to add * to exclude list:

D:\*
E:\*

[Dirk_Mueller]

Thanks for your answers.

Marianne - this is new in 7.1.0.4 ???

[Marianne]

We first saw this in NBU 7.0. See http://www.symantec.com/docs/TECH125205

Still no fix.  

[Marianne]

Hi Dirk

Thanks for the Solution, but Andy was first in this post:

https://www-secure.symantec.com/connect/forums/client-7104#comment-9261681

Please move the solution?

[CRZ]

Hi, sorry I'm late.

Can anyone confirm/deny that this is still an issue (or not) in 7.5.0.x?  I'm having trouble figuring out where/if it was fixed myself (which is...troubling?)

[mph999]

Hi Chris, do you want to borrow my server ... ;0)