Activity overview
Latest activity by icy
I have downloaded the latest release (eval) and I am happy to see that this problem is no more !!! Well done RedGate team. Now we can test this thoroughly / comments
I have downloaded the latest release (eval) and I am happy to see that this problem is no more !!! Well done RedGate team. Now we can test this thoroughly
The tests that I ran:
[passed]. local sql2005 express db
[passed]. local sqlCE db
[passed]. local sql2005 (not express) db
[passed]. Remote sqlCE db
[failed]. remote sql2005 express db
[failed]. remote sql2005
[failed]. remote sql2008 (this database is my own web site's database server. It's hosted on a hosting facility and has nothing to do with AD security issues. The host name is an IP address and the connection is not secured)
In all the tests, I ran first without profiler, saw the data in the datagrid, and then tried to run it again with profiler and saw the crash. For your information a screenshot is also attached.
Briefly, when the database to which you are trying to connect is on another computer (except the CE database, that one did not matter) then as soon as you set the ConnectionString property of the connection object, the profiler crashes. You don't even need to do anything on the connection: no need to open, execute. Just say conn.ConnectionString = "connstring" and the profiler will crash.
My environment:
/***********************************************************/XP Prof SP3
AVG Antivirus
Microsoft Security Essentials
Personal Firewall TURNED OFF
Behind local NAT
/***********************************************************/
Microsoft Visual Studio 2008
Version 9.0.21022.8 RTM
Microsoft .NET Framework
Version 3.5 SP1 / comments
The tests that I ran:
[passed]. local sql2005 express db
[passed]. local sqlCE db
[passed]. local sql2005 (not express) db
[passed]. Remote sqlCE db
[failed]. remote sql2005 express db
[failed]. re...
I am experiencing the exact same issue. I have narrowed it down to SQL access methodology. Though I could not exactly pinpoint where the issue lies. First and foremost, I am sure that this is NOT what it seems. There is no instability, memory corruption or any other type of issue with the application that I am monitoring. I am doing this merely out of curiosity.
I was doing a search on this particular error when I came across this thread. I will try to create a small project for the RedGate guys to recreate the issue and post it here.
Here's what I know so far:
If you create a local datastore (SqlCe) and access it, then there is no problem.
If you try to access a database on another server, then you have a problem.
This may be because of windows security issues - Active Directory etc. So far, changing the connection string to various models did not help circumvent the problem (TCP/IP, NamedPipes, Trusted Security, No-Trusted Security etc). / comments
I am experiencing the exact same issue. I have narrowed it down to SQL access methodology. Though I could not exactly pinpoint where the issue lies. First and foremost, I am sure that this is NOT w...