Hi all,
we have a strange problem in SQL2000 SP3a with SQLTransaction's.
When running SQL Profiler the duration for some SQLTransactions (Commit) are
over six seconds, but the individual SQL statements (sp's) are executed at n
o
time at all.
I've used sp_lock but there are no locks.
Here's an extract from SQLProfiler:
SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
15:30:34.683 DTCXact 16335154 sa
Any Ideas ?
Regards Tommy S.Check out master..sysprocesses and find out what the waittypes are
to determine what is causing the extended commit operation.
is the Tlog file on the same disk as the data file . .how busy is the server
?
is this constantly reproduceable? or is it intermittent?
HTH
"Tommy S?derkvist" wrote:
> Hi all,
> we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> When running SQL Profiler the duration for some SQLTransactions (Commit) a
re
> over six seconds, but the individual SQL statements (sp's) are executed at
no
> time at all.
> I've used sp_lock but there are no locks.
> Here's an extract from SQLProfiler:
> SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> 15:30:34.683 DTCXact 16335154 sa
> Any Ideas ?
> Regards Tommy S.
>|||Thanks,
I will try to check out the waittypes the next time I see a long running
transaction.
Yes, the log and the datafile are located on the same disk.
The CPU's (4 of them) are almost idle.
The problem is intermittent and it doesn't seem to be dependent on the
number of users, it can occur at early evening when the number of users
decrease significant.
/Tommy
"Olu Adedeji" wrote:
[vbcol=seagreen]
> Check out master..sysprocesses and find out what the waittypes are
> to determine what is causing the extended commit operation.
> is the Tlog file on the same disk as the data file . .how busy is the serv
er?
> is this constantly reproduceable? or is it intermittent?
> HTH
> "Tommy S?derkvist" wrote:
>|||"Tommy S?derkvist" <TommySderkvist@.discussions.microsoft.com> schrieb im
Newsbeitrag news:72BF587D-E3CF-41FE-9EC8-5681C62E472B@.microsoft.com...
> Thanks,
> I will try to check out the waittypes the next time I see a long running
> transaction.
> Yes, the log and the datafile are located on the same disk.
> The CPU's (4 of them) are almost idle.
> The problem is intermittent and it doesn't seem to be dependent on the
> number of users, it can occur at early evening when the number of users
> decrease significant.
My guess would be that you have an IO bottleneck which makes tx log
writing slow. You could use perfmon to verify this theory.
robert
[vbcol=seagreen]
> /Tommy
> "Olu Adedeji" wrote:
>
server?[vbcol=seagreen]
(Commit) are[vbcol=seagreen]
executed at no[vbcol=seagreen]
Showing posts with label strange. Show all posts
Showing posts with label strange. Show all posts
Friday, March 30, 2012
Long running SQLTransaction
Hi all,
we have a strange problem in SQL2000 SP3a with SQLTransaction's.
When running SQL Profiler the duration for some SQLTransactions (Commit) are
over six seconds, but the individual SQL statements (sp's) are executed at no
time at all.
I've used sp_lock but there are no locks.
Here's an extract from SQLProfiler:
SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
15:30:34.683 DTCXact 16335154 sa
Any Ideas ?
Regards Tommy S.Check out master..sysprocesses and find out what the waittypes are
to determine what is causing the extended commit operation.
is the Tlog file on the same disk as the data file . .how busy is the server?
is this constantly reproduceable? or is it intermittent?
HTH
"Tommy Söderkvist" wrote:
> Hi all,
> we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> When running SQL Profiler the duration for some SQLTransactions (Commit) are
> over six seconds, but the individual SQL statements (sp's) are executed at no
> time at all.
> I've used sp_lock but there are no locks.
> Here's an extract from SQLProfiler:
> SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> 15:30:34.683 DTCXact 16335154 sa
> Any Ideas ?
> Regards Tommy S.
>|||Thanks,
I will try to check out the waittypes the next time I see a long running
transaction.
Yes, the log and the datafile are located on the same disk.
The CPU's (4 of them) are almost idle.
The problem is intermittent and it doesn't seem to be dependent on the
number of users, it can occur at early evening when the number of users
decrease significant.
/Tommy
"Olu Adedeji" wrote:
> Check out master..sysprocesses and find out what the waittypes are
> to determine what is causing the extended commit operation.
> is the Tlog file on the same disk as the data file . .how busy is the server?
> is this constantly reproduceable? or is it intermittent?
> HTH
> "Tommy Söderkvist" wrote:
> > Hi all,
> > we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> > When running SQL Profiler the duration for some SQLTransactions (Commit) are
> > over six seconds, but the individual SQL statements (sp's) are executed at no
> > time at all.
> > I've used sp_lock but there are no locks.
> > Here's an extract from SQLProfiler:
> > SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> > 15:30:34.683 DTCXact 16335154 sa
> > Any Ideas ?
> > Regards Tommy S.
> >|||"Tommy Söderkvist" <TommySderkvist@.discussions.microsoft.com> schrieb im
Newsbeitrag news:72BF587D-E3CF-41FE-9EC8-5681C62E472B@.microsoft.com...
> Thanks,
> I will try to check out the waittypes the next time I see a long running
> transaction.
> Yes, the log and the datafile are located on the same disk.
> The CPU's (4 of them) are almost idle.
> The problem is intermittent and it doesn't seem to be dependent on the
> number of users, it can occur at early evening when the number of users
> decrease significant.
My guess would be that you have an IO bottleneck which makes tx log
writing slow. You could use perfmon to verify this theory.
robert
> /Tommy
> "Olu Adedeji" wrote:
> > Check out master..sysprocesses and find out what the waittypes are
> > to determine what is causing the extended commit operation.
> >
> > is the Tlog file on the same disk as the data file . .how busy is the
server?
> > is this constantly reproduceable? or is it intermittent?
> >
> > HTH
> >
> > "Tommy Söderkvist" wrote:
> >
> > > Hi all,
> > > we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> > > When running SQL Profiler the duration for some SQLTransactions
(Commit) are
> > > over six seconds, but the individual SQL statements (sp's) are
executed at no
> > > time at all.
> > > I've used sp_lock but there are no locks.
> > > Here's an extract from SQLProfiler:
> > > SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> > > 15:30:34.683 DTCXact 16335154 sa
> > > Any Ideas ?
> > > Regards Tommy S.
> > >
we have a strange problem in SQL2000 SP3a with SQLTransaction's.
When running SQL Profiler the duration for some SQLTransactions (Commit) are
over six seconds, but the individual SQL statements (sp's) are executed at no
time at all.
I've used sp_lock but there are no locks.
Here's an extract from SQLProfiler:
SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
15:30:34.683 DTCXact 16335154 sa
Any Ideas ?
Regards Tommy S.Check out master..sysprocesses and find out what the waittypes are
to determine what is causing the extended commit operation.
is the Tlog file on the same disk as the data file . .how busy is the server?
is this constantly reproduceable? or is it intermittent?
HTH
"Tommy Söderkvist" wrote:
> Hi all,
> we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> When running SQL Profiler the duration for some SQLTransactions (Commit) are
> over six seconds, but the individual SQL statements (sp's) are executed at no
> time at all.
> I've used sp_lock but there are no locks.
> Here's an extract from SQLProfiler:
> SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> 15:30:34.683 DTCXact 16335154 sa
> Any Ideas ?
> Regards Tommy S.
>|||Thanks,
I will try to check out the waittypes the next time I see a long running
transaction.
Yes, the log and the datafile are located on the same disk.
The CPU's (4 of them) are almost idle.
The problem is intermittent and it doesn't seem to be dependent on the
number of users, it can occur at early evening when the number of users
decrease significant.
/Tommy
"Olu Adedeji" wrote:
> Check out master..sysprocesses and find out what the waittypes are
> to determine what is causing the extended commit operation.
> is the Tlog file on the same disk as the data file . .how busy is the server?
> is this constantly reproduceable? or is it intermittent?
> HTH
> "Tommy Söderkvist" wrote:
> > Hi all,
> > we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> > When running SQL Profiler the duration for some SQLTransactions (Commit) are
> > over six seconds, but the individual SQL statements (sp's) are executed at no
> > time at all.
> > I've used sp_lock but there are no locks.
> > Here's an extract from SQLProfiler:
> > SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> > 15:30:34.683 DTCXact 16335154 sa
> > Any Ideas ?
> > Regards Tommy S.
> >|||"Tommy Söderkvist" <TommySderkvist@.discussions.microsoft.com> schrieb im
Newsbeitrag news:72BF587D-E3CF-41FE-9EC8-5681C62E472B@.microsoft.com...
> Thanks,
> I will try to check out the waittypes the next time I see a long running
> transaction.
> Yes, the log and the datafile are located on the same disk.
> The CPU's (4 of them) are almost idle.
> The problem is intermittent and it doesn't seem to be dependent on the
> number of users, it can occur at early evening when the number of users
> decrease significant.
My guess would be that you have an IO bottleneck which makes tx log
writing slow. You could use perfmon to verify this theory.
robert
> /Tommy
> "Olu Adedeji" wrote:
> > Check out master..sysprocesses and find out what the waittypes are
> > to determine what is causing the extended commit operation.
> >
> > is the Tlog file on the same disk as the data file . .how busy is the
server?
> > is this constantly reproduceable? or is it intermittent?
> >
> > HTH
> >
> > "Tommy Söderkvist" wrote:
> >
> > > Hi all,
> > > we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> > > When running SQL Profiler the duration for some SQLTransactions
(Commit) are
> > > over six seconds, but the individual SQL statements (sp's) are
executed at no
> > > time at all.
> > > I've used sp_lock but there are no locks.
> > > Here's an extract from SQLProfiler:
> > > SQLTransaction Commit 6796 5 2005-03-04 15:30:27.887 2005-03-04
> > > 15:30:34.683 DTCXact 16335154 sa
> > > Any Ideas ?
> > > Regards Tommy S.
> > >
Long running SQLTransaction
Hi all,
we have a strange problem in SQL2000 SP3a with SQLTransaction's.
When running SQL Profiler the duration for some SQLTransactions (Commit) are
over six seconds, but the individual SQL statements (sp's) are executed at no
time at all.
I've used sp_lock but there are no locks.
Here's an extract from SQLProfiler:
SQLTransactionCommit679652005-03-04 15:30:27.8872005-03-04
15:30:34.683DTCXact16335154sa
Any Ideas ?
Regards Tommy S.
Check out master..sysprocesses and find out what the waittypes are
to determine what is causing the extended commit operation.
is the Tlog file on the same disk as the data file . .how busy is the server?
is this constantly reproduceable? or is it intermittent?
HTH
"Tommy S?derkvist" wrote:
> Hi all,
> we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> When running SQL Profiler the duration for some SQLTransactions (Commit) are
> over six seconds, but the individual SQL statements (sp's) are executed at no
> time at all.
> I've used sp_lock but there are no locks.
> Here's an extract from SQLProfiler:
> SQLTransactionCommit679652005-03-04 15:30:27.8872005-03-04
> 15:30:34.683DTCXact16335154sa
> Any Ideas ?
> Regards Tommy S.
>
|||Thanks,
I will try to check out the waittypes the next time I see a long running
transaction.
Yes, the log and the datafile are located on the same disk.
The CPU's (4 of them) are almost idle.
The problem is intermittent and it doesn't seem to be dependent on the
number of users, it can occur at early evening when the number of users
decrease significant.
/Tommy
"Olu Adedeji" wrote:
[vbcol=seagreen]
> Check out master..sysprocesses and find out what the waittypes are
> to determine what is causing the extended commit operation.
> is the Tlog file on the same disk as the data file . .how busy is the server?
> is this constantly reproduceable? or is it intermittent?
> HTH
> "Tommy S?derkvist" wrote:
|||"Tommy S?derkvist" <TommySderkvist@.discussions.microsoft.com> schrieb im
Newsbeitrag news:72BF587D-E3CF-41FE-9EC8-5681C62E472B@.microsoft.com...
> Thanks,
> I will try to check out the waittypes the next time I see a long running
> transaction.
> Yes, the log and the datafile are located on the same disk.
> The CPU's (4 of them) are almost idle.
> The problem is intermittent and it doesn't seem to be dependent on the
> number of users, it can occur at early evening when the number of users
> decrease significant.
My guess would be that you have an IO bottleneck which makes tx log
writing slow. You could use perfmon to verify this theory.
robert
[vbcol=seagreen]
> /Tommy
> "Olu Adedeji" wrote:
server?[vbcol=seagreen]
(Commit) are[vbcol=seagreen]
executed at no[vbcol=seagreen]
we have a strange problem in SQL2000 SP3a with SQLTransaction's.
When running SQL Profiler the duration for some SQLTransactions (Commit) are
over six seconds, but the individual SQL statements (sp's) are executed at no
time at all.
I've used sp_lock but there are no locks.
Here's an extract from SQLProfiler:
SQLTransactionCommit679652005-03-04 15:30:27.8872005-03-04
15:30:34.683DTCXact16335154sa
Any Ideas ?
Regards Tommy S.
Check out master..sysprocesses and find out what the waittypes are
to determine what is causing the extended commit operation.
is the Tlog file on the same disk as the data file . .how busy is the server?
is this constantly reproduceable? or is it intermittent?
HTH
"Tommy S?derkvist" wrote:
> Hi all,
> we have a strange problem in SQL2000 SP3a with SQLTransaction's.
> When running SQL Profiler the duration for some SQLTransactions (Commit) are
> over six seconds, but the individual SQL statements (sp's) are executed at no
> time at all.
> I've used sp_lock but there are no locks.
> Here's an extract from SQLProfiler:
> SQLTransactionCommit679652005-03-04 15:30:27.8872005-03-04
> 15:30:34.683DTCXact16335154sa
> Any Ideas ?
> Regards Tommy S.
>
|||Thanks,
I will try to check out the waittypes the next time I see a long running
transaction.
Yes, the log and the datafile are located on the same disk.
The CPU's (4 of them) are almost idle.
The problem is intermittent and it doesn't seem to be dependent on the
number of users, it can occur at early evening when the number of users
decrease significant.
/Tommy
"Olu Adedeji" wrote:
[vbcol=seagreen]
> Check out master..sysprocesses and find out what the waittypes are
> to determine what is causing the extended commit operation.
> is the Tlog file on the same disk as the data file . .how busy is the server?
> is this constantly reproduceable? or is it intermittent?
> HTH
> "Tommy S?derkvist" wrote:
|||"Tommy S?derkvist" <TommySderkvist@.discussions.microsoft.com> schrieb im
Newsbeitrag news:72BF587D-E3CF-41FE-9EC8-5681C62E472B@.microsoft.com...
> Thanks,
> I will try to check out the waittypes the next time I see a long running
> transaction.
> Yes, the log and the datafile are located on the same disk.
> The CPU's (4 of them) are almost idle.
> The problem is intermittent and it doesn't seem to be dependent on the
> number of users, it can occur at early evening when the number of users
> decrease significant.
My guess would be that you have an IO bottleneck which makes tx log
writing slow. You could use perfmon to verify this theory.
robert
[vbcol=seagreen]
> /Tommy
> "Olu Adedeji" wrote:
server?[vbcol=seagreen]
(Commit) are[vbcol=seagreen]
executed at no[vbcol=seagreen]
Friday, March 23, 2012
Logshipping
Hi
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
Uday
Hi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday
|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>
|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>
|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
[vbcol=seagreen]
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...[vbcol=seagreen]
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
>
>
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
Uday
Hi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday
|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>
|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>
|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
[vbcol=seagreen]
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...[vbcol=seagreen]
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
>
>
Logshipping
Hi
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We alread
y
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
[vbcol=seagreen]
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't fin
d
> the network path name. The full backup job says that it ran for 1:26minute
s
> before it failed. But i see transaction log for every 15minutes in that 1:
26
> minutes. Usually when the ful backup starts, the transaction log back star
ts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
>|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...[vbcol=seagreen]
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
>
>sql
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We alread
y
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
[vbcol=seagreen]
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't fin
d
> the network path name. The full backup job says that it ran for 1:26minute
s
> before it failed. But i see transaction log for every 15minutes in that 1:
26
> minutes. Usually when the ful backup starts, the transaction log back star
ts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
>|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...[vbcol=seagreen]
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
>
>sql
Wednesday, March 21, 2012
Logshipping
Hi
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
> > Hi
> > Can you see how did the last LOG restore to the database? What happened?
> >
> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > > Hi
> > >
> > > I have a strange problem started happening in my log shipping. The
> > > database
> > > went to suspect/loading/read-only mode in the middle of the night.
> > > Can't see any particular reason in the sql srever errorlog.
> > >
> > > One thing i noticed in th msdb..backupset. This table did not have an
> > > entry
> > > for anyother transaction log that happened after the last transaction log
> > > that got applid to the database. But the logshipping copy job is fine and
> > > it
> > > copies all the logs. Something broken internally in the logshpping. I
> > > looked
> > > online for anymore info. Apparently there was a hotfix before SP3. We
> > > already
> > > have sp3 on this server.
> > >
> > > Did anyone experience this problem?
> > > Any idea?
> > > Any kind of help is appreciated.
> > >
> > > Thanks
> > > Uday
> >
> >
> >|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>> Hi Uri
>> I also notice something strange.
>> The database that was doing the full backup job failed.
>> It actually did do the backup. But the job failed saying that it can't
>> find
>> the network path name. The full backup job says that it ran for
>> 1:26minutes
>> before it failed. But i see transaction log for every 15minutes in that
>> 1:26
>> minutes. Usually when the ful backup starts, the transaction log back
>> starts
>> but never does the transaction log backup until its completed. Right.
>> This is strange.
>> --Uday
>> "Uri Dimant" wrote:
>> > Hi
>> > Can you see how did the last LOG restore to the database? What
>> > happened?
>> >
>> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
>> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>> > > Hi
>> > >
>> > > I have a strange problem started happening in my log shipping. The
>> > > database
>> > > went to suspect/loading/read-only mode in the middle of the night.
>> > > Can't see any particular reason in the sql srever errorlog.
>> > >
>> > > One thing i noticed in th msdb..backupset. This table did not have an
>> > > entry
>> > > for anyother transaction log that happened after the last transaction
>> > > log
>> > > that got applid to the database. But the logshipping copy job is fine
>> > > and
>> > > it
>> > > copies all the logs. Something broken internally in the logshpping. I
>> > > looked
>> > > online for anymore info. Apparently there was a hotfix before SP3. We
>> > > already
>> > > have sp3 on this server.
>> > >
>> > > Did anyone experience this problem?
>> > > Any idea?
>> > > Any kind of help is appreciated.
>> > >
>> > > Thanks
>> > > Uday
>> >
>> >
>> >|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> > Ignore this reply.
> > It did say that it waited for the hour that it took for the full backup to
> > fail.
> > I had the backup file. Bayut the job reported failure.
> >
> > Back to square onw. I am not sure what happened.
> > Help please
> > Ud
> >
> > "Udayasree" wrote:
> >
> >> Hi Uri
> >>
> >> I also notice something strange.
> >> The database that was doing the full backup job failed.
> >> It actually did do the backup. But the job failed saying that it can't
> >> find
> >> the network path name. The full backup job says that it ran for
> >> 1:26minutes
> >> before it failed. But i see transaction log for every 15minutes in that
> >> 1:26
> >> minutes. Usually when the ful backup starts, the transaction log back
> >> starts
> >> but never does the transaction log backup until its completed. Right.
> >> This is strange.
> >>
> >> --Uday
> >>
> >> "Uri Dimant" wrote:
> >>
> >> > Hi
> >> > Can you see how did the last LOG restore to the database? What
> >> > happened?
> >> >
> >> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> >> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> >> > > Hi
> >> > >
> >> > > I have a strange problem started happening in my log shipping. The
> >> > > database
> >> > > went to suspect/loading/read-only mode in the middle of the night.
> >> > > Can't see any particular reason in the sql srever errorlog.
> >> > >
> >> > > One thing i noticed in th msdb..backupset. This table did not have an
> >> > > entry
> >> > > for anyother transaction log that happened after the last transaction
> >> > > log
> >> > > that got applid to the database. But the logshipping copy job is fine
> >> > > and
> >> > > it
> >> > > copies all the logs. Something broken internally in the logshpping. I
> >> > > looked
> >> > > online for anymore info. Apparently there was a hotfix before SP3. We
> >> > > already
> >> > > have sp3 on this server.
> >> > >
> >> > > Did anyone experience this problem?
> >> > > Any idea?
> >> > > Any kind of help is appreciated.
> >> > >
> >> > > Thanks
> >> > > Uday
> >> >
> >> >
> >> >
>
>sql
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
> > Hi
> > Can you see how did the last LOG restore to the database? What happened?
> >
> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > > Hi
> > >
> > > I have a strange problem started happening in my log shipping. The
> > > database
> > > went to suspect/loading/read-only mode in the middle of the night.
> > > Can't see any particular reason in the sql srever errorlog.
> > >
> > > One thing i noticed in th msdb..backupset. This table did not have an
> > > entry
> > > for anyother transaction log that happened after the last transaction log
> > > that got applid to the database. But the logshipping copy job is fine and
> > > it
> > > copies all the logs. Something broken internally in the logshpping. I
> > > looked
> > > online for anymore info. Apparently there was a hotfix before SP3. We
> > > already
> > > have sp3 on this server.
> > >
> > > Did anyone experience this problem?
> > > Any idea?
> > > Any kind of help is appreciated.
> > >
> > > Thanks
> > > Uday
> >
> >
> >|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>> Hi Uri
>> I also notice something strange.
>> The database that was doing the full backup job failed.
>> It actually did do the backup. But the job failed saying that it can't
>> find
>> the network path name. The full backup job says that it ran for
>> 1:26minutes
>> before it failed. But i see transaction log for every 15minutes in that
>> 1:26
>> minutes. Usually when the ful backup starts, the transaction log back
>> starts
>> but never does the transaction log backup until its completed. Right.
>> This is strange.
>> --Uday
>> "Uri Dimant" wrote:
>> > Hi
>> > Can you see how did the last LOG restore to the database? What
>> > happened?
>> >
>> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
>> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>> > > Hi
>> > >
>> > > I have a strange problem started happening in my log shipping. The
>> > > database
>> > > went to suspect/loading/read-only mode in the middle of the night.
>> > > Can't see any particular reason in the sql srever errorlog.
>> > >
>> > > One thing i noticed in th msdb..backupset. This table did not have an
>> > > entry
>> > > for anyother transaction log that happened after the last transaction
>> > > log
>> > > that got applid to the database. But the logshipping copy job is fine
>> > > and
>> > > it
>> > > copies all the logs. Something broken internally in the logshpping. I
>> > > looked
>> > > online for anymore info. Apparently there was a hotfix before SP3. We
>> > > already
>> > > have sp3 on this server.
>> > >
>> > > Did anyone experience this problem?
>> > > Any idea?
>> > > Any kind of help is appreciated.
>> > >
>> > > Thanks
>> > > Uday
>> >
>> >
>> >|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> > Ignore this reply.
> > It did say that it waited for the hour that it took for the full backup to
> > fail.
> > I had the backup file. Bayut the job reported failure.
> >
> > Back to square onw. I am not sure what happened.
> > Help please
> > Ud
> >
> > "Udayasree" wrote:
> >
> >> Hi Uri
> >>
> >> I also notice something strange.
> >> The database that was doing the full backup job failed.
> >> It actually did do the backup. But the job failed saying that it can't
> >> find
> >> the network path name. The full backup job says that it ran for
> >> 1:26minutes
> >> before it failed. But i see transaction log for every 15minutes in that
> >> 1:26
> >> minutes. Usually when the ful backup starts, the transaction log back
> >> starts
> >> but never does the transaction log backup until its completed. Right.
> >> This is strange.
> >>
> >> --Uday
> >>
> >> "Uri Dimant" wrote:
> >>
> >> > Hi
> >> > Can you see how did the last LOG restore to the database? What
> >> > happened?
> >> >
> >> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> >> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> >> > > Hi
> >> > >
> >> > > I have a strange problem started happening in my log shipping. The
> >> > > database
> >> > > went to suspect/loading/read-only mode in the middle of the night.
> >> > > Can't see any particular reason in the sql srever errorlog.
> >> > >
> >> > > One thing i noticed in th msdb..backupset. This table did not have an
> >> > > entry
> >> > > for anyother transaction log that happened after the last transaction
> >> > > log
> >> > > that got applid to the database. But the logshipping copy job is fine
> >> > > and
> >> > > it
> >> > > copies all the logs. Something broken internally in the logshpping. I
> >> > > looked
> >> > > online for anymore info. Apparently there was a hotfix before SP3. We
> >> > > already
> >> > > have sp3 on this server.
> >> > >
> >> > > Did anyone experience this problem?
> >> > > Any idea?
> >> > > Any kind of help is appreciated.
> >> > >
> >> > > Thanks
> >> > > Uday
> >> >
> >> >
> >> >
>
>sql
Wednesday, March 7, 2012
Login to SQL Server management studio
Hi,
I am facing a strange behavior during loging in to SQL server mangement studio.
Whenever I install SQL server express, various protocols like Named Pipe and TCP/IP and SQL browser are disabled by default. But still I am able to log in to SQL Server throguh Management studio.
But when I try to log in to SQL server throguh one of my applications, it allows me to log in to it only for one time. From next time onwards, I am not able to log in to SQL server neither through my application nor through Management studio.
I connect to SQL server using "machine name"\"Instance name". Machine name is the name of machine on my office LAN.
PS: Once this problem occurs, I can log in to SQL server if I use "localhost" instead of "machine name".
Any suggestions would be tremendously helpful.
Regards
-Orion
SQL Express supports connecting through Shared Memory, which is a local connectivity protocol that is used by the SQL Native Client. This is how you're connecting with Management Studio. I can't tell you what the problem is with your application as you have not provided an error message or error log.
Mike
|||Hi Mike,
Thanks for the reply.
>>
I can't tell you what the problem is with your application as you have not provided an error message or error log
>>
Following are the details of the exception thrown by SQL server.
{"State:08001,Native:6,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] State:01000,Native:11004,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]"}
The problem is when it allows my application to connect to SQL Server only once. After this, I need to enable TCP/IP protocol for any subsequent connection through my application or SQL Server management studio.
Regards,
Orion
Hi Orion,
Could you define what you mean by "subsequent connections through my application"? Are you talking about a single application creating multiple threads connecting to SQL Server? Are these different copies of the same application being run by other users on other computers? What is the connection string you're using from your application?
I don't recognize that error, is there any more descirptive text?
Mike
Login succeeded followed by Logon Failed
We are experiencing some strange behaviour on SQL Server 2000. Certain
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.
Friday, February 24, 2012
Login Problems using .net 2 Login Control
Hi There,
I have a really strange problem. I am creating a website with an administration back end. We have a seperate sql 2000 server which we are using hold authentication credientials (after having used the aspnet_regsql.exe to setup the appropriate tables.
When testing the application on the local machine, everything works fine. The web admin works, I can login, I can retrieve data to display on the rest of the site. Once uploaded to the live environment things change.
I can still connect to the sql server i.e. I have information being displayed on the public area of the site which is coming from the sql 2000 db. I can type in the incorrect login details to the admin section of the site and the system will return an error, which is correct as well, however, if I type in the correct login information, the page hangs for awhile and then displays this error: My question is, why is it doing this when it works find on my local box and the DB connection is actually working on other parts of the site? Can anyone help?
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Make sure TCP/IP activated as a connection method to the sql server and firewall doesn't block the connection.
|||HI.
There is no firewall between the two servers and TCP/IP is enabled. The fact is, a connection is working elsewhere on the site, but the login just doesnt work.
|||How do you know the connection is working? Do you mean the conneciton can be established to the remote SQL 2000 instance? You can turn on Audit Login for the SQL 2000 instance (right click the instance in Enterprise Manager->check Properties->switch to Security tab->change the Audit Level to All->restart server, then if there is any login failure, you can find the login failure error message in SQL ERRORLOGs.|||I think I have figured out what the problem is. I had the membership data source defined but not the roles, this meant that the roles were being stored in the sqlexpress DB while the membership details were being stored on SQL 2000. On my local machine, it could see both DB but when uploaded to the servers (that do not support sqlexpress DB) it was failing to connect once a successful login was taking place and roles needed to be allocated.
Pity the error reported gave no indication of what the problem really was.
Now I am having issues with creating the necessary permissions tables on the server. Once I get it all going and tested, I will clost this post as being solved.
Login problem by not being in sysadmin group
Hi All
I experience a very strange login problem:
I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.
All is working well.
The moment remove sysadmin group from this login, i start getting errors:
Login failed for user 'test1'
... when I login from remote server. If I login from the same host - it continues with no problem.
When I go to sql server configuration manager, I see next:
sql native client configuration(32bit):
shared memeory enabled
tcp/ip enabled
named pipes enabled
VIA disabled
The same settings from sql server 2005 network configuration / protocols for mssqlserver
sql native client configuration / client protocols
sql 2005 surface area configuration / remote connections is configured:
local and remote connections (checked), using both tcp/ip and named pipes.
Does anybody have a clue?
What is the default database for your login?
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Hi Wesley
Default db is named 'test'. I made sure login has default db and can browse it.
|||Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.
-Sue
Login problem by not being in sysadmin group
Hi All
I experience a very strange login problem:
I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.
All is working well.
The moment remove sysadmin group from this login, i start getting errors:
Login failed for user 'test1'
... when I login from remote server. If I login from the same host - it continues with no problem.
When I go to sql server configuration manager, I see next:
sql native client configuration(32bit):
shared memeory enabled
tcp/ip enabled
named pipes enabled
VIA disabled
The same settings from sql server 2005 network configuration / protocols for mssqlserver
sql native client configuration / client protocols
sql 2005 surface area configuration / remote connections is configured:
local and remote connections (checked), using both tcp/ip and named pipes.
Does anybody have a clue?
What is the default database for your login?
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Hi Wesley
Default db is named 'test'. I made sure login has default db and can browse it.
|||Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.
-Sue
Monday, February 20, 2012
Login problem
Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempts
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!
Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'.
> When looking in the security log on the sql server, we can see logon attempts
> by the local account from the client computer?! If logon to the same client
> with a domain account, everything works fine. My belief was that when using
> 'sql server auth', windows security had nothing to do with it.. am I wrong.
> Thanks for Your help!
|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>
|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you need to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). And perhaps you don't get
this validation at the Windows level when you login locally? You can check Client Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecting
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempts
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!
Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'.
> When looking in the security log on the sql server, we can see logon attempts
> by the local account from the client computer?! If logon to the same client
> with a domain account, everything works fine. My belief was that when using
> 'sql server auth', windows security had nothing to do with it.. am I wrong.
> Thanks for Your help!
|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>
|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you need to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). And perhaps you don't get
this validation at the Windows level when you login locally? You can check Client Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecting
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
Login problem
Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempt
s
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, pr
operties, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4.
No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'
.
> When looking in the security log on the sql server, we can see logon attem
pts
> by the local account from the client computer?! If logon to the same clien
t
> with a domain account, everything works fine. My belief was that when usin
g
> 'sql server auth', windows security had nothing to do with it.. am I wrong
.
> Thanks for Your help!|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server,
properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you n
eed to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). An
d perhaps you don't get
this validation at the Windows level when you login locally? You can check C
lient Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecti
ng
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
>
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempt
s
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, pr
operties, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4.
No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'
.
> When looking in the security log on the sql server, we can see logon attem
pts
> by the local account from the client computer?! If logon to the same clien
t
> with a domain account, everything works fine. My belief was that when usin
g
> 'sql server auth', windows security had nothing to do with it.. am I wrong
.
> Thanks for Your help!|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server,
properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you n
eed to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). An
d perhaps you don't get
this validation at the Windows level when you login locally? You can check C
lient Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecti
ng
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
>
Login problem
Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempts
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'.
> When looking in the security log on the sql server, we can see logon attempts
> by the local account from the client computer?! If logon to the same client
> with a domain account, everything works fine. My belief was that when using
> 'sql server auth', windows security had nothing to do with it.. am I wrong.
> Thanks for Your help!|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> > Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> > we are experiencing som strange problems. If we login to a klient with a
> > local account, open query analyzer and try to login using 'sql server
> > authentication', it does not work 'access denied or server does not exist'.
> > When looking in the security log on the sql server, we can see logon attempts
> > by the local account from the client computer?! If logon to the same client
> > with a domain account, everything works fine. My belief was that when using
> > 'sql server auth', windows security had nothing to do with it.. am I wrong.
> >
> > Thanks for Your help!
>|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you need to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). And perhaps you don't get
this validation at the Windows level when you login locally? You can check Client Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecting
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
>> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Erik" <Erik@.discussions.microsoft.com> wrote in message
>> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>> > Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
>> > we are experiencing som strange problems. If we login to a klient with a
>> > local account, open query analyzer and try to login using 'sql server
>> > authentication', it does not work 'access denied or server does not exist'.
>> > When looking in the security log on the sql server, we can see logon attempts
>> > by the local account from the client computer?! If logon to the same client
>> > with a domain account, everything works fine. My belief was that when using
>> > 'sql server auth', windows security had nothing to do with it.. am I wrong.
>> >
>> > Thanks for Your help!
>>
we are experiencing som strange problems. If we login to a klient with a
local account, open query analyzer and try to login using 'sql server
authentication', it does not work 'access denied or server does not exist'.
When looking in the security log on the sql server, we can see logon attempts
by the local account from the client computer?! If logon to the same client
with a domain account, everything works fine. My belief was that when using
'sql server auth', windows security had nothing to do with it.. am I wrong.
Thanks for Your help!Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> we are experiencing som strange problems. If we login to a klient with a
> local account, open query analyzer and try to login using 'sql server
> authentication', it does not work 'access denied or server does not exist'.
> When looking in the security log on the sql server, we can see logon attempts
> by the local account from the client computer?! If logon to the same client
> with a domain account, everything works fine. My belief was that when using
> 'sql server auth', windows security had nothing to do with it.. am I wrong.
> Thanks for Your help!|||Hi Tibor,
Thanks for your your reply.
The server is set up in mixed mode.
Strangly enough, if I connect to a share on the sql server with a domain
account (still logged on with a local account), I have no problem connecting
with the sql login I used earlier...
I've heard rumors that others are also experiencing this problem after
applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
with their reply.
By the way Tibor, I'm attending one of your classes at cornerstone on nov
4th, see you there :-)
Regards,
Erik
"Tibor Karaszi" wrote:
> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Erik" <Erik@.discussions.microsoft.com> wrote in message
> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
> > Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
> > we are experiencing som strange problems. If we login to a klient with a
> > local account, open query analyzer and try to login using 'sql server
> > authentication', it does not work 'access denied or server does not exist'.
> > When looking in the security log on the sql server, we can see logon attempts
> > by the local account from the client computer?! If logon to the same client
> > with a domain account, everything works fine. My belief was that when using
> > 'sql server auth', windows security had nothing to do with it.. am I wrong.
> >
> > Thanks for Your help!
>|||Hej Erik,
Perhaps IPC$ has anything to do with it? If you are using Named Pipes, you need to be able to use
IPC$ (at least this is how it used to work, not sure whether it changed). And perhaps you don't get
this validation at the Windows level when you login locally? You can check Client Network Utility on
the client whether you are using NP or IP Sockets.
See you in Nov :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Erik" <Erik@.discussions.microsoft.com> wrote in message
news:046970B4-5E32-42CA-812C-7183D197E76B@.microsoft.com...
> Hi Tibor,
> Thanks for your your reply.
> The server is set up in mixed mode.
> Strangly enough, if I connect to a share on the sql server with a domain
> account (still logged on with a local account), I have no problem connecting
> with the sql login I used earlier...
> I've heard rumors that others are also experiencing this problem after
> applying sp4. Anyhow, I've registered a case with Microsoft, I'll get back
> with their reply.
> By the way Tibor, I'm attending one of your classes at cornerstone on nov
> 4th, see you there :-)
> Regards,
> Erik
> "Tibor Karaszi" wrote:
>> Perhaps SQL Server is in "Windows Only" mode? EM, right-click the server, properties, security.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Erik" <Erik@.discussions.microsoft.com> wrote in message
>> news:4ABD6C8E-8341-44E6-B00D-58D0BDAD7C5C@.microsoft.com...
>> > Hi all, We have installed a new Win2003Server sp1 with sql2000server sp4. No
>> > we are experiencing som strange problems. If we login to a klient with a
>> > local account, open query analyzer and try to login using 'sql server
>> > authentication', it does not work 'access denied or server does not exist'.
>> > When looking in the security log on the sql server, we can see logon attempts
>> > by the local account from the client computer?! If logon to the same client
>> > with a domain account, everything works fine. My belief was that when using
>> > 'sql server auth', windows security had nothing to do with it.. am I wrong.
>> >
>> > Thanks for Your help!
>>
Subscribe to:
Posts (Atom)