This looks like the "Twilight Zone" for me !!!
Thats odd, but funny, kind of funny ... :)
You have 171 (more or less) answers to the
same question, but it looks like none of them
That is a little bit scary. :)
You are in the unknown dimension.
The most interesting one for myself...
Dar - 4/15/2005 12:00:00 AM
I've had this problem a couple of times now.
The error is just not recognised by Microsoft at all, so you're on your own.
This is what I would do in your case:
1. Take the older one and register properly on the server.
Check if it still works.
2. Unregister the older one in the server and check in the
"Registry" to remove everything about your component.
Use search in the "Registry Editor".
3. Open the older project on VB on the development machine
and ensure "Binary Compatibility".
4. Compile the new component.
5. Copy the component to the server and check security ACL.
The user which the server is running on should have read
access to your component .dll
6. Register properly the component on the server.
7. Shutdown (power-off) the server and restart.