[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.inetserver.asp.general

http://www.felix-timber.de/8.htmoiboqu

insinaipt

12/27/2013 4:30:00 PM

[url=http://www.felix-timber....]moncler daunenmantel[/url]mtpc
osselmih
oxzyrxjo
jdycovtu
[url=http://www.felix-timber...]moncler weste herren[/url]ijxq
tjanzkzj
azyqmcmn
tvmesvkh
[url=http://www.felix-timber....]http://www.felix-timber....[/url]pwta
negsfpxs
czbklpfj
jatfrdmt
[url=http://www.felix-timber...]http://www.felix-timber...[/url]ytjs
kaioccoh
tkhgcdzh
vpulcoss
[url=http://www.felix-timber....]moncler jacke[/url]ynbd
euhnfvoo
cfwsarzb
lpfszbxx
danjdgfd
bjpkuswg
kavycjvs
tvlyzgwg
2 Answers

=?Utf-8?B?QW5keQ==?=

10/5/2007 6:39:00 PM

0

We are also experiencing the exact same issue. Please let us know the
resolution. Many Many thanks...!

Cheers
Andy

"Jason Coombes" wrote:

> Hi Carlos,
>
> The person handling the support ticket has been in daily contact with me
> (experience of MS tech support has been excellent) but nothing to report so
> far. I did find an application which had accidentally been configured so
> that the 2nd server was being connected to first instead of as a failover.
> This has made it harder for me to prove my case but now that has been
> resolved connections are still hitting the 2nd db server.
>
> Am expecting another call back tomorrow when we will review the logs again
> and see if any further connections have been rejected.
>
> Jason.
>
> "Carlos Mendon??a" wrote:
>
> > Dear Jason,
> >
> > We too confirm that the event is being reported in the Application log in
> > the exact same way you saw it. It doesn't say much more regarding the
> > problem, though. What has been Microsoft's position regarding this issue so
> > far? Has there been any progress whatsoever in the ticket you have opened?
> >
> > Thanks,
> >
> > Carlos Mendon??a
> >
> > "Jason Coombes" <Jason Coombes@discussions.microsoft.com> wrote in message
> > news:93115343-E17E-452B-982A-78DC4EDC353D@microsoft.com...
> > > We have been experiencing the exact same issue and currently have an open
> > > support ticket with Microsoft to try and resolve the problem.
> > >
> > > Interestingly, if you check the application event logs on the failover sql
> > > server you should see an event like this (at the exact time of the .Net
> > error
> > > 6):
> > >
> > > Event Type: Failure Audit
> > > Event Source: MSSQLSERVER
> > > Event Category: (4)
> > > Event ID: 18456
> > > Date: 4/09/2007
> > > Time: 1:59:39 PM
> > >
> > > The event log entry also reports the client IP address and the username
> > that
> > > tried to connect but for security reasons I'm not including that
> > information
> > > here.
> > >
> > > We have 4 installations that use database mirroring and all of them are
> > > experiencing this issue. I don't believe we have installed KB928365 due
> > to
> > > strict testing policy on windows updates prior to rollout on production
> > > servers.
> > >
> > > Jason.
> > >
> > > "Carlos Mendon??a" wrote:
> > >
> > > > Hello,
> > > >
> > > > I work at a Hosting Company in Brazil and we have been experiencing
> > issues
> > > > with managed applications using .NET Framework 2.0 that connect to SQL
> > > > Server 2005 databases with a failover partner. These issues started
> > > > happening after we have applied KB928365
> > > > (http://support.microsoft.com...).
> > > >
> > > > The issue is an System.InvalidOperationException that is thrown every
> > once
> > > > in a while when connecting to the databases. The message is 'Internal
> > ..Net
> > > > Framework Data Provider error 6.'. Both Operating System (Windows 2003)
> > and
> > > > databases (SQL Server 2005) are up to date, including all Security
> > Updates
> > > > and Service Packs.
> > > >
> > > > Although not many use failover partners to be able to reproduce the
> > issue,
> > > > we have identified people with similar problems while searching for the
> > > > exception message in the major search engines. Additionally, the same
> > > > problem has been reported at 'microsoft.public.dotnet.framework.adonet',
> > but
> > > > it has been suggested that KB928365 should be removed, which is not an
> > > > option for us considering the security concerns involved.
> > > >
> > > > I am posting in the newsgroups in hope of reaching someone from the .NET
> > > > team to report this issue. I think it may be a bug, but it could also be
> > > > some configuration requirement that KB928365 introduced. In either case,
> > it
> > > > is an issue that affect big databases and I believe that we should pay
> > > > special attention to the case.
> > > >
> > > > I am not familiar with the process of reporting an issue to the .NET
> > and/or
> > > > SQL Server teams and I would appreciate if someone could give me a hint.
> > > >
> > > > I thank you in advance.
> > > >
> > > > Carlos Mendon??a
> > > >
> > > >
> > > >
> >
> >
> >

=?Utf-8?B?QW5keQ==?=

10/17/2007 7:26:00 PM

0

Our app server and database servers are on different boxes. We do have the
failover setup on the database though.

Anyone has the solution?

"alexey.volochenko@gmail.com" wrote:

> On Oct 5, 11:39 am, Andy <A...@discussions.microsoft.com> wrote:
> > We are also experiencing the exact same issue. Please let us know the
> > resolution. Many Many thanks...!
> >
> > Cheers
> > Andy
> >
> > "Jason Coombes" wrote:
> > > Hi Carlos,
> >
> > > The person handling the support ticket has been in daily contact with me
> > > (experience of MS tech support has been excellent) but nothing to report so
> > > far. I did find an application which had accidentally been configured so
> > > that the 2nd server was being connected to first instead of as a failover.
> > > This has made it harder for me to prove my case but now that has been
> > > resolved connections are still hitting the 2nd db server.
> >
> > > Am expecting another call back tomorrow when we will review the logs again
> > > and see if any further connections have been rejected.
> >
> > > Jason.
> >
> > > "Carlos Mendon??a" wrote:
> >
> > > > Dear Jason,
> >
> > > > We too confirm that the event is being reported in the Application log in
> > > > the exact same way you saw it. It doesn't say much more regarding the
> > > > problem, though. What has been Microsoft's position regarding this issue so
> > > > far? Has there been any progress whatsoever in the ticket you have opened?
> >
> > > > Thanks,
> >
> > > > Carlos Mendon??a
> >
> > > > "Jason Coombes" <Jason Coom...@discussions.microsoft.com> wrote in message
> > > >news:93115343-E17E-452B-982A-78DC4EDC353D@microsoft.com...
> > > > > We have been experiencing the exact same issue and currently have an open
> > > > > support ticket with Microsoft to try and resolve the problem.
> >
> > > > > Interestingly, if you check the application event logs on the failover sql
> > > > > server you should see an event like this (at the exact time of the ..Net
> > > > error
> > > > > 6):
> >
> > > > > Event Type: Failure Audit
> > > > > Event Source: MSSQLSERVER
> > > > > Event Category: (4)
> > > > > Event ID: 18456
> > > > > Date: 4/09/2007
> > > > > Time: 1:59:39 PM
> >
> > > > > The event log entry also reports the client IP address and the username
> > > > that
> > > > > tried to connect but for security reasons I'm not including that
> > > > information
> > > > > here.
> >
> > > > > We have 4 installations that use database mirroring and all of them are
> > > > > experiencing this issue. I don't believe we have installed KB928365 due
> > > > to
> > > > > strict testing policy on windows updates prior to rollout on production
> > > > > servers.
> >
> > > > > Jason.
> >
> > > > > "Carlos Mendon??a" wrote:
> >
> > > > > > Hello,
> >
> > > > > > I work at a Hosting Company in Brazil and we have been experiencing
> > > > issues
> > > > > > with managed applications using .NET Framework 2.0 that connect to SQL
> > > > > > Server 2005 databases with a failover partner. These issues started
> > > > > > happening after we have applied KB928365
> > > > > > (http://support.microsoft.com...).
> >
> > > > > > The issue is an System.InvalidOperationException that is thrown every
> > > > once
> > > > > > in a while when connecting to the databases. The message is 'Internal
> > > > ..Net
> > > > > > Framework Data Provider error 6.'. Both Operating System (Windows 2003)
> > > > and
> > > > > > databases (SQL Server 2005) are up to date, including all Security
> > > > Updates
> > > > > > and Service Packs.
> >
> > > > > > Although not many use failover partners to be able to reproduce the
> > > > issue,
> > > > > > we have identified people with similar problems while searching for the
> > > > > > exception message in the major search engines. Additionally, the same
> > > > > > problem has been reported at 'microsoft.public.dotnet.framework.adonet',
> > > > but
> > > > > > it has been suggested that KB928365 should be removed, which is not an
> > > > > > option for us considering the security concerns involved.
> >
> > > > > > I am posting in the newsgroups in hope of reaching someone from the .NET
> > > > > > team to report this issue. I think it may be a bug, but it could also be
> > > > > > some configuration requirement that KB928365 introduced. In either case,
> > > > it
> > > > > > is an issue that affect big databases and I believe that we should pay
> > > > > > special attention to the case.
> >
> > > > > > I am not familiar with the process of reporting an issue to the .NET
> > > > and/or
> > > > > > SQL Server teams and I would appreciate if someone could give me a hint.
> >
> > > > > > I thank you in advance.
> >
> > > > > > Carlos Mendon??a
>
> I had the same issue, and found a fix for it. In my case i was running
> the app on the same server as the principal database. Application
> referenced to itself via hostname and caused an issue, unless you
> specify an IP of machine instead, and/or move the app to a completely
> different server.
>
>