"No Such Interface Supported" Exception 0x80004002 - HELP!

AAAAARRRRRRRRRRRGGGGGGGGG!

I finally figure out why I can't connect to the SQLEXPRESS on this computer (technically, I was a remote connection), get everything installed (Advanced edition), and then...

It keeps telling me that "No Such Interface is Supported" and "Unable to cast COM object of type "System._ComObject" to Interface type..."

I grabbed it in a screen capture and will try to get it to a server tonight when I get home.

Any ideas on this problem?

Jason

http://members.cox.net/pamela444/errorwindow.jpg

Well, it won't let me insert a link, but the photo's at that URL.

|||

This error comes from VS. Have you determined if SQL Express is functioning correctly by itself?

On the computer you are getting this error, try connecting to SQL Express using SQLCmd, open a command prompt and type:

SQLCmd -S <machinename>\sqlexpress -Q "select @.@.version"

If this returns the version of your server, then you know that SQL Express is functioning correctly and that you have it configured to accept the connection if you're trying to access it remotely. Info on configuring remote connections is at:

914277 How to configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

"Max Database Size" issue

I'm creating a new SQL CE database on a desktop computer via merge replication with an existing SQL 2005 database. The original database is appx. 270MB, so I set the "max database size" parameter in my connection string to 1024 (which should indicate a max SQL CE database size of 1GB). The initial replication works fine. However, when I open the database from my custom application (which does NOT specify a max database size in its connection string), I get an exception telling me that the database has grown beyond its maximum size.

The documentation for SQL CE seems to indicate that the "max database size" connection string parameter is only examined when the database is originally created or compacted. Is this true, or do I need to specify max database size in the connection string even when opening an existing database?

Thanks in advance for any help or direction anyone can offer!

For the final word on Max database size, see http://blogs.msdn.com/sqlservercompact/archive/2007/06/13/the-story-of-max-database-size-connection-string-parameter.aspx

"Either the computer running IIS is out of memory, or an incorrect session ID was sent in a

Has anyone ever seen this error? It's listed as SSCE_M_INVALIDRSCBID on this page.

That site also advises very clearly:

"If you experience any errors with the prefix "Internal error" while you use SQL Server Compact Edition, try the operation again as the error might not reproduce. If the error appears again, you should immediately contact Microsoft Product Support Services. The internal errors cannot be resolved by common troubleshooting techniques."

IIS 6.0 is located on a separate server from SQL Server 2005. Installation instructions from Microsoft.com were followed to a "T". I've spent a full day with our client's DBA enabling/disabling various settings on these two servers. Replication works fine if IIS is running on the same server. I'm confident our publication and web-sync settings are correct.

There is no firewall between these servers. They are on the same local network.

Have you been able to resolve this, noluck? I encountered the same problem. I posted it here before finding your post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1601966&SiteID=1

In my case, IIS and SQL Server are on the same machine.

"Either the computer running IIS is out of memory, or an incorrect session ID was sent in a

Has anyone ever seen this error? It's listed as SSCE_M_INVALIDRSCBID on this page.

That site also advises very clearly:

"If you experience any errors with the prefix "Internal error" while you use SQL Server Compact Edition, try the operation again as the error might not reproduce. If the error appears again, you should immediately contact Microsoft Product Support Services. The internal errors cannot be resolved by common troubleshooting techniques."

IIS 6.0 is located on a separate server from SQL Server 2005. Installation instructions from Microsoft.com were followed to a "T". I've spent a full day with our client's DBA enabling/disabling various settings on these two servers. Replication works fine if IIS is running on the same server. I'm confident our publication and web-sync settings are correct.

There is no firewall between these servers. They are on the same local network.

Have you been able to resolve this, noluck? I encountered the same problem. I posted it here before finding your post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1601966&SiteID=1

In my case, IIS and SQL Server are on the same machine.