COM Surrogate Errors
in [ASP .NET]
|
Prev: Ajax.net Development to Production = javascript error (baseType)
Next: ThreadAbortException at ExportToHttpResponse()
From: lhardwick69 on 24 Mar 2007 18:33 [ i was having this problem and formatted my pc 3 times since vista has been released--on the forth time i was getting kind of mad and thought about going back to vista-as i never had this problem--but my dad fixed it for me---go to program that causes the com surrogate error to pop up - start--programs--find program--right click-go to properties on the window that pops up--instead of running it as compatable for windows xp--look toward lower part of box and run it as administrator--click ok/apply and boom..problem fixed..if it isnt that program its a program that deals with video..so go through and do that with all programs that deal with video..it fixed my probleem it never did this to me on xp but vista it did and where vista is trying to be the most secure version ever--it requires a lot more treaking to work right--any other questions--email me at lhardwick69 @ frontiernet.netand if i can help i will QUOTE]-Originally posted by Bruce Barker - *vb6 com objects are apartment model com objects. this mean all access to the com object must be from the same thread that created it. asp.net is thread agile (switches threads during processing), vb6 components are not supported by default. you can set the aspcompat attribute (if a web page) or create you own thread for calling the vb6 object. note: .net web services do not support vb6 com objects, you must create a controlling thread. -- bruce (sqlwork.com) "neilt100" <neilt100(a)discussions.microsoft.com> wrote in message news:5478DFC8-80B8-43E9-A0C7-77F6886F92D4(a)microsoft.com... > Am running Win XP SP2 with Classic ASP+VB6 dll's alongside ASP.NET+C# > dll's. > > I keep getting the following error . 'COM Surrogate encountered a problem > and needs to shut down'. This requires me to do an IISReset and re-start > whatever I was doing, which is extremely frustrating. Google reveals that > this is a pretty common type of error but does not point me to any kind of > solution to it. MS's knowledge base appears pretty silent on this issue. > > I have just rebuilt my PC from scratch and installed mostly MS products > (save the Oracle 9.2.04 ODP) so I cannot understand what could be the > cause > of this problem. So if anybody has any advice (aside from installing W2K > or > W2003) that may be of help I greatly appreciate it? > > Neil > > Further info > ======= > I have saved the conents of both the following ... > C:\DOCUME~1\b9995730\LOCALS~1\Temp\WER05bb.dir00\dllhost.exe.mdmp > C:\DOCUME~1\b9995730\LOCALS~1\Temp\WER05bb.dir00\appcompat.txt > ... and can send on. > > A restricted width extract from appcompat.txt is as follows ... > > <?xml version="1.0" encoding="UTF-16"?> > <DATABASE> > <EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM" > <MATCHING_FILE NAME="advapi32.dll" SIZE="616960" > <MATCHING_FILE NAME="gdi32.dll" SIZE="278016" CHE > <MATCHING_FILE NAME="kernel32.dll" SIZE="983552" > <MATCHING_FILE NAME="ntdll.dll" SIZE="708096" CHE > <MATCHING_FILE NAME="ole32.dll" SIZE="1281536" CH > <MATCHING_FILE NAME="oleaut32.dll" SIZE="553472" > <MATCHING_FILE NAME="shell32.dll" SIZE="8384000" > <MATCHING_FILE NAME="user32.dll" SIZE="577024" CH > <MATCHING_FILE NAME="wininet.dll" SIZE="656384" C > <MATCHING_FILE NAME="winsock.dll" SIZE="2864" CHE > </EXE> > </DATABASE> > > * -- lhardwick69 ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ |