Reply to thread

Message: [QUOTE="Guest, post: 9505603"] Hello WenYuan; Yes, I'm still watching ;) A little more detail for your research: we have a standard ASP site that instantiates a .Net DLL as a COM component (using Server.CreateObject()) for backend work, primarily for database access (using ADO.Net). Resetting IIS universally resolves the issue (or has so far, at least). The error we see says "Column <ColumnName> does not belong to table <TableName>". The values of ColumnName and TableName vary depending on what page is being accessed when the error occurs, and there is no consistency to it at all that we've been able to discover. Universally the column referenced in the error message does indeed exist in the referenced table. Is that a better level of detail? [/QUOTE]