TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
leonard.whitehead
NA
1
0
Runtime Callable Wrappers
Oct 14 2004 11:18 AM
Creating RCW's seems easy enough but have you ever tried to work out why one works on your machine but not when uploaded to a server? I have a webiste that uses a COM component to process card payments. I cretaed an RCW to point to it and added a the correct reference in ASP.NET. I still get the following stack trace: Server Error in '/RacketShop' Application. ------------------------------------------------------------------------ -------- QueryInterface for interface NETVSPHttpUtility._VSPHttpRequest failed. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidCastException: QueryInterface for interface NETVSPHttpUtility._VSPHttpRequest failed WHAT I'VE TRIED 1 - I've checked the the web for has <%@Page AspCompat="true"%> 2 - I've checked that the hosting compnay has used regsvr32 on the com dll 3 - I've verified all of the parameters being passed to the query interface are legitimate 4 - I've checked that the asp-net account has read and execute permissions on the dlls 5 - I've checked that the MDAC version is high enough WHAT I KNOW 1 - That the error can be recreated on any machine if you unregister the protx dll, however the hosting compnay assured me that the dll is registered and that other customers can use the component ok WHAT I'D LIKE To hear from someone who has gone through similiar. It doesn't seem possible to run a dsissassembler remotes to verify the interfaces in the RCW but this error has cost me two weeks and I give my left pinkie for a solution.
Reply
Answers (
0
)
error handling
scripting and ASP.Net