> >function TIBOCustomService.ParseInteger(var RunLen: Integer):

Integer;

> >begin
> > result := isc_vax_integer(OutputBuffer + RunLen, 4);
> > RunLen := RunLen + 4;
> >end;
>
> Doubtful. All this does is ensure that 64-bit integers don't cause
> an overflow.

Everything seems to be fine the Service Activates.
But then it calls IsServiceRunning it dies.

>
> I have TIBOBackupService working fine with Classic 1.5.3. Have you
> paid proper attention to the requirement for local connections to
> Classic to be through localhost? That's the usual cause of problems
> in the transition from Superserver to Classic.

Changed the ServerName from ComputerName to Localhost
there were no changes in the way things happenned.

>
> A bit off-topic for this list, but pay attention to the following
> when using the IBOAdmin components:
>
> 1) if you're mixing a service component with a data access
> application, don't be fooled into thinking that the service

component

> will jump onto a valid connection that you have already made to a
> database. The service components create their own IB_Connection

from

> the properties you set in Server, DatabaseName and Protocol in the
> service component. Protocol must be cpTCP_IP. Under the hood, it
> will all be converted to a remote service_mgr attachment, the only
> kind that works for Classic.
>

My Protocol is cpTCP_IP.

I am getting error "Lock time out on wait transaction"

> 2) clean out all the cruft that gets written into the Params

property

> at design-time. Otherwise there's a high chance that your previous
> wrong settings will just sit there waiting to bite you at runtime.
>
> ./heLen
>

I only set Username and password parameters.

Regards,

Robert.