Re: [ADSM-L] Win32 client won't start
2008-03-10 17:08:57
Check to see if you have anything in the dsierror.log. Also look in your Event
Viewer for errors. There may be a problem in your dsm.opt file.
Johnny
>>> "Large, Matthew : Barclays Wealth" <matthew.large AT BARCLAYS DOT COM>
>>> 3/10/2008 9:03 AM >>>
Hi ADSMers,
I've not seen this kind of problem before - I have a Win32 client (5.4.1.0)
which can ping it's Solaris10 TSM server (5.4.1.2), but fails to connect.
Starting dsmc from the command line brings me no prompt, TSM appears to
deliver nothing to the screen, or the dsmerror.log.
So I ran a service trace and it all seems normal up to:
plug-in name : PISNAPSHOT
Library Path : .\plugins\pivss.dll
plug-in Version : 5.4.1.0
Plugin specific-info : <Provider:VSS> <Stack Position:Volume Manager>
<SnapFuncMap:0x00002008>
===========================================
03/10/2008 13:42:13.335 [005696] [8340] : piLicense.cpp ( 174):
piLoadLicense() entry
03/10/2008 13:42:13.335 [005696] [8340] : piLicense.cpp ( 324):
piLoadLicense() exit, no license file required
03/10/2008 13:42:13.350 [005696] [8340] : optservices.cpp (5368):
poEnvVarInit: Entry
03/10/2008 13:42:13.350 [005696] [8340] : psfsinfo.cpp (3545):
psGetUncName(): Enter with path 'C:\'
03/10/2008 13:42:13.350 [005696] [8340] : vssreq.cpp ( 761):
VssRequestor::InitializeVss(): reqType=3, usageType=3
03/10/2008 13:42:13.350 [005696] [8340] : vssreq.cpp ( 832):
VssRequestor::InitializeVss(): VSS[CreateVssBackupComponents]
03/10/2008 13:42:13.350 [005696] [8340] : vssreq.cpp ( 851):
VssRequestor::InitializeVss(): VSS[InitializeForBackup]
03/10/2008 13:42:13.366 [005696] [8340] : vssreq.cpp ( 869):
VssRequestor::InitializeVss(): VSS[SetBackupState]
03/10/2008 13:42:13.366 [005696] [8340] : vssreq.cpp (3339):
VssQuerySystemWriters(): Entry --- querying for files to exclude from
backup..
03/10/2008 13:42:13.366 [005696] [8340] : vssreq.cpp (3345):
VSS[GatherWriterMetadata]
03/10/2008 13:42:13.366 [005696] [8340] : vssreq.cpp (8407):
VssRequestor::QueryStatus(): VSS - waiting for asynchronous operation to
complete for caller 'VssQuerySystemWriters()'
At which point (after 1 minute) I ctrl-c out and this is written:
unknown thread -1================>
03/10/2008 13:43:36.362 [005696] [8740] : psthread.cpp (1099):
??????????????????????????????????????
??03/10/2008 13:43:36.362 [005696] [8740] : psthread.cpp (1108):
ConsoleEventHandler(): Cleaning up and terminating Process ...
I'm unable to stop the dsmcad service through the normal method (Error 1053:
The service did not respond to the start or control request in a timely
fashion); terminating the process from TaskManager is the only way to stop
it. It starts happily enough but doesn't write anything to the
dsmerror/sched.log. Dsm.exe also does nothing.
This is all I have to go on, so any help is hugely appreciated!
Many Thanks,
Matthew
This e-mail and any attachments are confidential and intended solely for the
addressee and may also be privileged or exempt from disclosure under applicable
law. If you are not the addressee, or have received this e-mail in error,
please notify the sender immediately, delete it from your system and do not
copy, disclose or otherwise act upon any part of this e-mail or its attachments.
Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising from
unauthorised access to, or interference with, any Internet communications by
any third party, or from the transmission of any viruses. Replies to this
e-mail may be monitored by the Barclays Group for operational or business
reasons.
Any opinion or other information in this e-mail or its attachments that does
not relate to the business of the Barclays Group is personal to the sender and
is not given or endorsed by the Barclays Group.
Barclays Bank PLC.Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.
Barclays Bank PLC is authorised and regulated by the Financial Services
Authority.
Individuals who have received this information in error or are not authorized
to receive it must promptly return or dispose of the information and notify the
sender. Those individuals are hereby notified that they are strictly prohibited
from reviewing, forwarding, printing, copying, distributing or using this
information in any way.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [ADSM-L] Win32 client won't start, Large, Matthew : Barclays Wealth
- Re: [ADSM-L] Win32 client won't start,
Johnny Lea <=
- Re: [ADSM-L] Win32 client won't start, Andrew Raibeck
- Re: [ADSM-L] Win32 client won't start, Large, Matthew : Barclays Wealth
- Re: [ADSM-L] Win32 client won't start, Ian-IT Smith
- Re: [ADSM-L] Win32 client won't start, Large, Matthew : Barclays Wealth
- Re: [ADSM-L] Win32 client won't start, Harry Redl
- Re: [ADSM-L] Win32 client won't start, Large, Matthew : Barclays Wealth
- Re: [ADSM-L] Win32 client won't start, Harry Redl
- Re: [ADSM-L] Win32 client won't start, Large, Matthew : Barclays Wealth
- [ADSM-L] Adding Encrypted stgpool, Large, Matthew : Barclays Wealth
- Re: [ADSM-L] Adding Encrypted stgpool, Richard Sims
|
|
|