I would uninstall the client, reboot, then search for any/all occurances
of the TSMUTIL1.DLL. If you find any...DELETE 'em!

Then re-install the client.

Bill Boyer
DSS, Inc.
On Wed, 2002-11-20 at 14:38, Qualls, Ted W {PBSG} wrote:
> you might try reloading your client code.
>
>
>
>
> Ted W. Qualls
> UNIX Enterprise Engineering
> PepsiCo Business Solutions Group
> 5080 Spectrum Drive
> Suite 600W
> Addison, TX 75001
> office: 972.376.7809
> pgr:    800.946.4645 pin 1090913
> cell:   469.682.1773
> email: ted.w.qualls AT fritolay DOT com
>
>
>
> -----Original Message-----
> From: Joshua Bassi [mailto:jbassi AT IHWY DOT COM]
> Sent: Wednesday, November 20, 2002 11:44 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Help Urgently needed
>
>
> That doesn't look good. I would recommend calling support at this point.
>
>
> --
> Joshua S. Bassi
> IBM Certified - AIX 4/5L, SAN, Shark
> Tivoli Certified Consultant - ADSM/TSM
> eServer Systems Expert -pSeries HACMP
>
> AIX, HACMP, Storage, TSM Consultant
> Cell (831) 595-3962
> jbassi AT ihwy DOT com
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Amini, Mehdi
> Sent: Wednesday, November 20, 2002 7:27 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Help Urgently needed
>
>
> When I try to create a scheduler service on a NT4 running TSM Version
> 4.2.31 I get this error:
>
>
> The procedure Entry Point TSMEnumDependentServiceEnd Could not be
> located in the Dynamic Link Library TMSUTIL1.DLL
>
> Please help
>
> Thanks
>
>
>
> Mehdi Amini
> LAN/WAN Engineer
> ValueOptions
> 12369 Sunrise Valley Drive
> Suite C
> Reston, VA 20191
> Phone: 703-390-6855
> Fax: 703-390-2581
>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error please notify the
> sender by email, delete and destroy this message and its attachments.
>
>
> **********************************************************************