Unable to create plan file

[devparveen]

Hello Everybody, we have TSM 5.4 on win2k3 ent.x64. We have just implement DRM but when PREPARE command run it shows unable to create plant file.Output for Q DRM , Q DRMSTATUS and Q actlog search=prepare attached here.
sm: ITSM01>q drmstatus

Recovery Plan Prefix: C:\DRM\PLAN
Plan Instructions Prefix: C:\DRM\INSTRUCTION
Replacement Volume Postfix: @
Primary Storage Pools: DISKPOOL OFFSITE
Copy Storage Pools: COPYPOOL
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 14 Day(s)
ecovery Plan File Expiration Days: 30 Day(s)
Check Label?: Yes
Process FILE Device Type?: No
Command File Name:
tsm: ITSM01>q drm

Volume Name State Last Update Automated
Date/Time LibName
---------------- ----------------- ------------------- -------------
280BFML4 Vault 08/23/2011 10:48:41
539BEPL4 Vault 08/17/2011 17:14:44
A00008L4 Vault 08/26/2011 09:46:10
CI1952L4 Vault 08/17/2011 17:15:48
276BFML4 Vault 08/24/2011 12:38:13

tsm: ITSM01>q actlog search=prepare

Date/Time Message
-------------------- ----------------------------------------------------------
08/26/2011 10:29:39 ANR2017I Administrator ADMIN issued command: PREPARE
(SESSION: 615)
08/26/2011 10:29:39 ANR0984I Process 14 for PREPARE started in the BACKGROUND
at 10:29:39. (SESSION: 615, PROCESS: 14)
08/26/2011 10:29:39 ANR6954E PREPARE: Unable to open file
'C:\DRM\PLAN.20110826.102939' for output. (SESSION: 615,
PROCESS: 14)
08/26/2011 10:29:39 ANR6951E PREPARE: Recovery plan file
C:\DRM\PLAN.20110826.102939 was not created. (SESSION:
615, PROCESS: 14)
08/26/2011 10:29:39 ANR0985I Process 14 for PREPARE running in the BACKGROUND
completed with completion state FAILURE at 10:29:39.
(SESSION: 615, PROCESS: 14)
08/26/2011 10:29:44 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG
search=prepare (SESSION: 615)

 

[cjhood]

Please do not ask a new unrelated question in an old thread. I've moved this post to its own thread.

 

[terlisimo]

Does the folder exist and does the user under which TSM instance is running have proper permissions for it?

You could use the Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645) to see what happens on the filesystem level.