Hello,
This is error common for win2003 server
11/16/2011 10:32:42 ANS1327W The snapshot operation for
'HAIFADC02\SystemState\NULL\
System State\SystemState' failed with error code: 4353.
Check the vssadmin writers status and in that if any writers are in waiting
for completion or are in faile
Hello seems to be VSS writers problem,there are 2 ways to solve the WMI
writers problem
1.if server is Win2003,then run the NT backup,which will refresh the
writers status
command:
ntbackup backup systemstate /f "C:\systemstate_backup.bkf"
2.you can restart the Windows mangement instrumention (
Seems to me Vss writers issue,Needs to reboot the server will help you to
fix the vss writers error and check with the respected Windows team about
the VSS writers status
On Mon, Jan 21, 2013 at 4:12 PM, Loon, EJ van - SPLXM wrote:
> Hmm...
> Just a wild guess, but could this be related?
> htt
Hello Mr.Zoltan,
This is know problem when the OS level and DB level upgrade happened,Seems
to be some links which are related to the language packages settings are
missed,so you based on the OS flovour of unix,you have check with them to
fix the issue.there will not be any impact on these files
Hello Guys,
There are 3 ways to fix the issue.
1)Restarting the Volume shadow copy services.
2)Take native NT backup using below command
ntbackup backup systemstate /f "C:\systemstate_backup.bkf"
3)If the above 2 options didn't help,restarting the server would help you!
Thank you!
Gopikrishn
SM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> gopi muppidi
> Sent: Friday, April 19, 2013 10:13 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Backup failing due to snap shot issue
>
> Hello Guys,
>
> There are 3 ways to fix the issue.
>
>
Hello Guys,
Seems to be which is backint connection issue,so you have reset the
password in following ways.
1)update the password on tsm server of the node as SID name as password
2)check the backint connection using following way
a)login as DB user (su - ora)
b) change to dbs directory
Hello
Which clearly shows that TCP/IP port is wrong,which should be 1500 in the
dsmserv.opt server option file
ANR1820E The server could not connect to the database manager by using *TCP/IP
port 51500*
*
*
Like below
=
dsmserv.opt
--
COMMmethodTCPIP
TCPPort
Hello,
For solaris nodes,you have to install TSM client packages in all the local
zones along with Global zone,that's why you are unable to see the /opt in
the local zones as the tsm client packages not yet installed on local zones.
Regards,
Gopi
On Thu, May 2, 2013 at 1:24 PM, Hans Christian R
Hello
I need the dsmerror.log and dsmsched.log files logs for last day since when
you modified the schedule's
in the dsmsched.log file,is the schedule still showing the start time is
17:00hrs or 22:00hrs,give me the logs
Cheers,
Gopikrishna
On Thu, May 2, 2013 at 3:29 PM, Schneider, Jim wrot
Hello
Seems to be this is DB2 Instance userid configuration issue.
Resolving the problem
To resolve this issue, check the following and make sure that they are
configured correctly. You will need to run the following commands to
validate if the configuration is correct.
db2set all
db2 list db
11 matches
Mail list logo
