Showing posts with label details. Show all posts
Showing posts with label details. Show all posts

Monday, March 19, 2012

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.
Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegr oups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>
|||Thnx for the post.

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknow
n
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unkn
own
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.

Sunday, February 26, 2012

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
>> All,
>> I have the below problem while attaching the database,
can
>> any one assist.
>> Thanks in advance.
>> --Error Details
>> Microsoft SQL-DMO(ODBC SQLState-HY000)
>> Error 3624
>> Location : recovery.C:2014
>> Expression: Curr-->log_length >0
>> SPID :53
>> ProcessorId: 1064
>> below is the last lines from Error Log
>> 2004-06-01 10:27:14.45 spid53 Stack Signature for
the
>> dump is 0x9A8706F6
>> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
>> File: <recovery.c>, line=2014
>> Failed Assertion = 'curr->log_length > 0'.
>> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
>> 20, State: 1.
>> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
>> 23, State: 7
>> 2004-06-01 10:27:15.93 spid53 An error occurred
while
>> processing the log for database 'UPSSISGR'..
>>
>> ...Mukund.R.L.
>>
>>
>.
>

Friday, February 17, 2012

Error 21776 when accessing sa account

I get the 21776 error when I try to view the sa account under
security/logins. I can click past it and still view and change account
details, but how do I get rid of the error. I have read about
out-of-sync users problem and have tried the suggested script:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'sa'
EXEC sp_droplogin 'TempOwner'
GO
However I don't know what to use for MyDatabase. Since I'm changing sa
account details I thought that I should point to master. You can't
change the owner of master. I'm a noob. What am I missing. I'm using
msde2000.
Tom
Error 21776: [SQL-DMO]The name 'dbo' was not found in the Users
Collection. If the name is a qualified name, use [] to seperate various
parts of the name, and try again.The error means that the owner of one or more of your user databases is
out-of-sync, probably due to a restore or attach.
You need to run sp_changedbowner in the context of your user database.
sp_changedbowner was corrected in SP3 so you don't need to temporarily
change ownership to a non-conflicting login.
The script below will change ownership for all user databases to 'sa':
DECLARE @.ChangeDBOwner nvarchar(4000)
DECLARE ChangeDBOwner CURSOR
LOCAL FAST_FORWARD READ_ONLY FOR
SELECT N'USE ' + CATALOG_NAME + N'
EXEC sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
OPEN ChangeDBOwner
WHILE 1 = 1
BEGIN
FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
IF @.@.FETCH_STATUS = -1 BREAK
EXEC(@.ChangeDBOwner)
END
CLOSE ChangeDBOwner
DEALLOCATE ChangeDBOwner
GO
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Tom Wells" <noemail@.nowhere.none> wrote in message
news:%23kHB4HWeDHA.3160@.tk2msftngp13.phx.gbl...
> I get the 21776 error when I try to view the sa account under
> security/logins. I can click past it and still view and change account
> details, but how do I get rid of the error. I have read about
> out-of-sync users problem and have tried the suggested script:
> USE MyDatabase
> EXEC sp_addlogin 'TempOwner'
> EXEC sp_changedbowner 'TempOwner'
> EXEC sp_changedbowner 'sa'
> EXEC sp_droplogin 'TempOwner'
> GO
> However I don't know what to use for MyDatabase. Since I'm changing sa
> account details I thought that I should point to master. You can't
> change the owner of master. I'm a noob. What am I missing. I'm using
> msde2000.
> Tom
> Error 21776: [SQL-DMO]The name 'dbo' was not found in the Users
> Collection. If the name is a qualified name, use [] to seperate
various
> parts of the name, and try again.
>|||I wish I understood better what I was doing but it worked. I used the
Query Analyzer and ran the script against each of my user databases.
After running the script the sa user showed up as the dbo of the database.
Thanks
Tom
Dan Guzman wrote:
> The error means that the owner of one or more of your user databases is
> out-of-sync, probably due to a restore or attach.
> You need to run sp_changedbowner in the context of your user database.
> sp_changedbowner was corrected in SP3 so you don't need to temporarily
> change ownership to a non-conflicting login.
> The script below will change ownership for all user databases to 'sa':
> DECLARE @.ChangeDBOwner nvarchar(4000)
> DECLARE ChangeDBOwner CURSOR
> LOCAL FAST_FORWARD READ_ONLY FOR
> SELECT N'USE ' + CATALOG_NAME + N'
> EXEC sp_changedbowner ''sa'''
> FROM INFORMATION_SCHEMA.SCHEMATA
> WHERE CATALOG_NAME NOT IN
> (
> 'master',
> 'model',
> 'msdb',
> 'tempdb',
> 'distribution'
> )
> OPEN ChangeDBOwner
> WHILE 1 = 1
> BEGIN
> FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
> IF @.@.FETCH_STATUS = -1 BREAK
> EXEC(@.ChangeDBOwner)
> END
> CLOSE ChangeDBOwner
> DEALLOCATE ChangeDBOwner
> GO
>|||The database owner SID is stored in 2 separate places - sysdatabases
(master database) and the 'dbo' row in the sysusers (user database).
The GUI tools misbehave when these get out of sync due to a restore or
attach. The sp_changedbowner script corrected the mismatch.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tom Wells" <noemail@.nowhere.none> wrote in message
news:euuMXy5eDHA.1056@.TK2MSFTNGP10.phx.gbl...
> I wish I understood better what I was doing but it worked. I used the
> Query Analyzer and ran the script against each of my user databases.
> After running the script the sa user showed up as the dbo of the
database.
> Thanks
> Tom
> Dan Guzman wrote:
> > The error means that the owner of one or more of your user databases
is
> > out-of-sync, probably due to a restore or attach.
> >
> > You need to run sp_changedbowner in the context of your user
database.
> > sp_changedbowner was corrected in SP3 so you don't need to
temporarily
> > change ownership to a non-conflicting login.
> >
> > The script below will change ownership for all user databases to
'sa':
> >
> > DECLARE @.ChangeDBOwner nvarchar(4000)
> > DECLARE ChangeDBOwner CURSOR
> > LOCAL FAST_FORWARD READ_ONLY FOR
> > SELECT N'USE ' + CATALOG_NAME + N'
> > EXEC sp_changedbowner ''sa'''
> > FROM INFORMATION_SCHEMA.SCHEMATA
> > WHERE CATALOG_NAME NOT IN
> > (
> > 'master',
> > 'model',
> > 'msdb',
> > 'tempdb',
> > 'distribution'
> > )
> > OPEN ChangeDBOwner
> > WHILE 1 = 1
> > BEGIN
> > FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
> > IF @.@.FETCH_STATUS = -1 BREAK
> > EXEC(@.ChangeDBOwner)
> > END
> > CLOSE ChangeDBOwner
> > DEALLOCATE ChangeDBOwner
> > GO
> >
>