When you do the mapping, it's done with the rights you are logged in with
(Administrator).
The system account doesn't have the same rights (in fact it usually has NO
rights to use network resources) and that is the account the TSM server
service is using.

Go to Windows Services, look at the Properties of the TSM server service.
Change its logon to an account that has rights to the shares you need to
access, the restart the service.



On Fri, Nov 21, 2008 at 8:29 AM, Richard van Denzel <RvanDenzel AT sltn DOT 
nl>wrote:

> Then it's still which account where? I'm using Administrator under Windows
> and map the share with sysadmin from the DD530.
>
> Met vriendelijke groet, with kind regards,
>
> Richard van Denzel.
>
> ________________________________
>
> From: ADSM: Dist Stor Manager on behalf of Henrik Vahlstedt
> Sent: Fri 11/21/2008 1:06 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] DataDomain problems
>
>
>
> I still belive it is an account, premission issue.
>
> -H.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Richard van Denzel
> Sent: den 21 november 2008 12:49
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] DataDomain problems
>
> Yes we are running as local Administrator for the server.
>
> We can map the share to a drive letter (we used K:) and we are then able
> to create maps/folders and/or files on the share.
>
> Met vriendelijke groet, with kind regards,
>
> Richard van Denzel.
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Henrik Vahlstedt
> Sent: 21 November 2008 11:38
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] DataDomain problems
>
> We use UNC names when we use Datadomain.
>
> Msg=8971 says "The server attempted to validate that the directory was
> accessible"
>
> If TSM server runs under Local System account, doeas Local system have
> access rights to the DD share? Test to run define devclass when TSM
> server is running undere your admin account.
>
>
> //Henrik
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Richard van Denzel
> Sent: den 21 november 2008 11:14
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] DataDomain problems
>
> Hi All,
>
>
>
> I'm trying to add a DataDomain DD530 (running DDR 4.5.2.5-76716) to a
> Windows (2003 SP2) TSM Server (5.5.1.0). I can add a CIFS share from the
> DD530 without problems and also create maps/folders and files on it from
> Windows.
>
>
>
> When I issue the following command from TSM:
>
>
>
> DEF DEVC DD_CLASS DEVT=FILE MAXCAP=200G DIR=K:\DDPool (K: being the
> mapped CIFS share)
>
>
>
> I get the following error:
>
>
>
> ANR8971E Unable to validate the directory name K:\DDPOOL for DEFINE
> DEVCLASS command.
>
> ANR8366E Define Devclass: Invalid value for DIRECTORY parameter.
>
>
>
> I also tried the UNC path (\\DD530\backup\DDPool
> <file:///\\DD530\backup\DDPool <file://dd530/backup/DDPool> > ) instead,
> but with the same results.
>
>
>
> I can use local disks from the TSM Server just fine for the FILE class
> (e.g. like C: or D:).
>
>
>
> Met vriendelijke groet, with kind regards,
>
>
>
> Richard van Denzel
>
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of
> the information or copying of this message is prohibited. If you are not
> the addressee, please notify the sender immediately by return e-mail and
> delete this message.
> Thank you.
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.
>