|
| Re: DLL REGISTER failure |
 |
Wed, 07 Mar 2007 08:32:58 -060 |
If the dll file is local for each machine then I suspect that the dll is
corrupt. If the dll is in shared directory on the server then I suspect
that system trouble with creating the necessary temp files. This would
indicate a possible permisions problem.
Chris Outlaw wrote:
> We have a .dll file (blat.dll) that fails at the REGISTER command on one
> machine (SB error code 165) but it works fine on two other computers on
the
> network (same files and same set-up). Other .dll files REGISTER and work
> perfectly on all three computers. The .dll files are accessed locally and
> all machine use Win2000.
>
>
>
> What could be causing this failure? What happens when the REGISTER command
> is executed?
>
>
>
> Thanks
>
|
| Post Reply
|
| DLL REGISTER failure |
 |
Wed, 7 Mar 2007 11:09:21 -0000 |
We have a .dll file (blat.dll) that fails at the REGISTER command on one
machine (SB error code 165) but it works fine on two other computers on the
network (same files and same set-up). Other .dll files REGISTER and work
perfectly on all three computers. The .dll files are accessed locally and
all machine use Win2000.
What could be causing this failure? What happens when the REGISTER command
is executed?
Thanks
|
| Post Reply
|
| Re: DLL REGISTER failure |
 |
Wed, 7 Mar 2007 16:55:09 -0000 |
I have now downgraded blat.dll from version 2.61 to 2.5 and it works. There
must be some incompatibility with blat.dll v. 2.61 lurking in the problem
machine.
Thanks for your help!
"Roland Bellington" <rbellington@ussoccer.org> wrote in message
news:esmi18$lph$1@ipx22096.ipxserver.de...
> If the dll file is local for each machine then I suspect that the dll is
> corrupt. If the dll is in shared directory on the server then I suspect
> that system trouble with creating the necessary temp files. This would
> indicate a possible permisions problem.
>
> Chris Outlaw wrote:
> > We have a .dll file (blat.dll) that fails at the REGISTER command on
one
> > machine (SB error code 165) but it works fine on two other computers
on
the
> > network (same files and same set-up). Other .dll files REGISTER and
work
> > perfectly on all three computers. The .dll files are accessed locally
and
> > all machine use Win2000.
> >
> >
> >
> > What could be causing this failure? What happens when the REGISTER
command
> > is executed?
> >
> >
> >
> > Thanks
> >
> >
|
| Post Reply
|
|
|
|
|
|
|
|
|
|