Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error 1812 - The specified image file did not contain a resource section

1,025 views
Skip to first unread message

John Filippi

unread,
Mar 1, 1999, 3:00:00 AM3/1/99
to
To All - I have run into this twice now on two seperate NT 4.0 servers
this happens when you use the service manager to start and stop the service
but works fine if i manually start through a shortcut. reinstalling does not
help does anyone
have any suggestions?

john filippi
applied data systems, inc.
jo...@adsi-fm.com


Leo Tohill

unread,
Mar 1, 1999, 3:00:00 AM3/1/99
to
>To All - I have run into this twice now on two seperate NT 4.0 servers
>this happens when you use the service manager to start and stop the service
>but works fine if i manually start through a shortcut. reinstalling does not
>help does anyone
>have any suggestions?


This error generally indicates a PATH
or system variable problem. Make sure that sqlany50\win32 is on the path. Verify the PATH avaialble
to the service.


HTH

Leo Tohill - Team Powersoft
-- Please post in newsgroup, not via email <

Jim Egan

unread,
Mar 1, 1999, 3:00:00 AM3/1/99
to
It may also indicate that you are pointing the db server at a database
file that isn't a database or doesn't exist.
--
Jim Egan [TeamPS]
Dynamic Data Solutions, Inc. http://www.dyn-data.com
Houston, TX

***********************************************************
Enterprise Applications in Your Future?
JumpStart '99 Enterprise Solutions Conference
http://www.JumpStart99.com
***********************************************************


John Filippi

unread,
Mar 3, 1999, 3:00:00 AM3/3/99
to
To All - Thank you for all your help, I went through all of the paths and
have even taken the switches down to the -n and the sademo.db still a
problem so i thought lets try a different name and it worked!!!!! Once I
started the service with a different name it came up just fine. Normally if
there is another sybase out there broadcasting the same name you error with
another service with that name already started, but there was not the case I
made sure of that. what I think happend is microsoft hung onto the name some
how, (thanks bill) so after a half hour of service with the new name I
switched back to the old name and we are set and works.. Again thank you for
your help


Jim Egan

unread,
Mar 4, 1999, 3:00:00 AM3/4/99
to
Ah, yes that can happen on Netware networks when starting the db server.
I've not heard of this happening with service names. Was anything still
showing up in the Task Manager?
0 new messages