HI
I have 2 SQL Servers 2000 enterprise version. I setup a transactional replication between them. There is a table using identity feature and set to not for replication. On the server A as publication, B as Subscriber. I created table in B manually and set the name conflict in article default to keep existing data. When it replicates at the first time, everything is fine, but if there is some data added to the table in Server A, the replication fails, saying cannot update indentity column.
I read about something on add Set Identity on/off thing. But I dont know which SP I should add this to. Please help. As detail as possible. Thanks.There is a bug in the Managed Range Identity system. In Merge Replication I have found that while creating a publication using range identities it will work only the first time. Changing settings such as Publisher range or subscriber range does not have an effect. Also, deleting the subscriptions and publications DOES NOT remove the constraints from the affected subscriber tables. Also, the entry for the database in the replication distribution DB table MSrepl_identity_range does not get deleted and therefore the next time the publication is run it will not take the correct settings. In order to successfully recreate the subscription you must delete the row(s) from the afore mentioned table and remove all constraints manually. Only then will it work. If the constraints are not removed the subscriber will show the identity range as used up and will demand a re-sync, and the re-sync will have no effect.
Applies to SQL Server 2000 All SPs
You MUST delete all publications on the affected database and subscriptions first, then run SP_RemoveDBReplication DBName on the publisher and subscribers first then follow the steps above. You can sp_help to see what constraints are on the tables.|||I am sorry, if I undertsand you correctly what you are saying is that I cannot have a replication set up for identity enabled table?|||Originally posted by cobraeyez
I am sorry, if I undertsand you correctly what you are saying is that I cannot have a replication set up for identity enabled table?
no, you can set it up. Just keep in mind that there is a bug in SQL Server relating to the identitiy managing subsystem. What you want to do is delete the pub, subscriptions, drop the Check Constraints on all the subscription tables, find the Identity_Range table in the Replication Distribution database and delete all entries for the database that you are working on. Then recreate the publication and subcription and you will be fine.|||hey. thanks that SP_RemoveDBReplication thing works. :)|||ok, maybe I speak too quick, I think the insert works, but the update doesn't . If I modify a record in the publisher the replication failed again.
And what I did for fix the insert record is remove the publications and subscriptions and ran that RemoveReplication command on the DBs, there is no records in MSrepl_indentity_range table for me to delete.|||ok. The article containing the identitiy field is not set to range identitiy. When you set up the publication you need to click the "..." button to the right of the article name, then click the "Identity Range" tab. Enter your values and click OK to start the Identitiy Ranging.|||thanks, you mean the table article property button (...) right? In there, there is no Identity Range Tab. There are 3 tabs in it. General, Command, Snapshot.|||You will only have that tab on articles that have an identitiy column. Are you sure the article has an Identitiy?|||yes, and I am using sql 2000, identity is enabled and set not for replication|||You've got much of suggestions to the question, but I hope this MSDN Link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) also gives you much insight to resolve.
HTH|||I had a similar problem and it was because I had triggers and DRI on the same table
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Thursday, March 22, 2012
Error 8102: Cannot Update Identity Column
Hi,
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.Originally posted by da_i256
Hi,
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.
check this thread:
http://dbforums.com/arch/7/2003/5/779346|||thanks, harshal_in...
then link did provide some insights into the matter.
anyone else got any idea?
thanks.|||Have you gone thru the MSDN link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) referred in the above post, it must have resolved with the workaround mentioned.|||Thanks guys...
the problem solved... :>sql
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.Originally posted by da_i256
Hi,
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.
check this thread:
http://dbforums.com/arch/7/2003/5/779346|||thanks, harshal_in...
then link did provide some insights into the matter.
anyone else got any idea?
thanks.|||Have you gone thru the MSDN link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) referred in the above post, it must have resolved with the workaround mentioned.|||Thanks guys...
the problem solved... :>sql
Sunday, March 11, 2012
error 614
One of our 6.5 servers is getting error 614 (A row on a page x was accessed that has an illegal length of y in database z.) However, we can read the specified tables with "select * from a" and can "select into" a new table from those tables with no errors reported. DBCC checkdb and newalloc show no problems. Has anyone else seen this behaviour? We are running diagnostics on the server and raid hardware to determine if those components have problems that might be causing the 614 errors.Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.|||Originally posted by achorozy
Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.
------------------------
Thanks for the reply.
Our server version is 6.50.422 which is a "post SP5" version. I considered the large Group By as a possible cause, but no software changes were made prior to the first occurance of the error. I'll double check with the analyst who supports the app to make sure though.
Thanks again.
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.|||Originally posted by achorozy
Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.
------------------------
Thanks for the reply.
Our server version is 6.50.422 which is a "post SP5" version. I considered the large Group By as a possible cause, but no software changes were made prior to the first occurance of the error. I'll double check with the analyst who supports the app to make sure though.
Thanks again.
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on â'main serverâ' (using job) and
start job on another MS SQL Server 6.5(â'standby serverâ'). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the â'standby serverâ' and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on â'main serverâ' (using job)
and
>start job on another MS SQL Server 6.5(â'standby serverâ'). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the â'standby serverâ' and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>> Hello,
>> This error message indicates database corruption. You may want to run
dbcc
>> checkdb on the original database to make sure it is OK. If so, there
might
>> be issues when copying database.
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>> If original database has problem, corruption issue might be caused by
>> hardware. Please check the following event log to see if there is any
>> related events on disk etc.
>There are no any disk related messages in eventlog.
>> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
>> that you upgrade to later version when possible.
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on â'main serverâ' (using job) and
start job on another MS SQL Server 6.5(â'standby serverâ'). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the â'standby serverâ' and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on â'main serverâ' (using job)
and
>start job on another MS SQL Server 6.5(â'standby serverâ'). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the â'standby serverâ' and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>> Hello,
>> This error message indicates database corruption. You may want to run
dbcc
>> checkdb on the original database to make sure it is OK. If so, there
might
>> be issues when copying database.
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>> If original database has problem, corruption issue might be caused by
>> hardware. Please check the following event log to see if there is any
>> related events on disk etc.
>There are no any disk related messages in eventlog.
>> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
>> that you upgrade to later version when possible.
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) an
d
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the follow
ing
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>
dbcc[vbcol=seagreen]
might[vbcol=seagreen]
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>
>There are no any disk related messages in eventlog.
>
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) an
d
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the follow
ing
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>
dbcc[vbcol=seagreen]
might[vbcol=seagreen]
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>
>There are no any disk related messages in eventlog.
>
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) and
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.
Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>
|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) and
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.
Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>
|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.
Friday, March 9, 2012
Error 500, Maximum concurrent users have reached
We are running three web sites in a clustered environment
WLBS. The web servers are connected to a Database Server
running MS SQL server enterprise edition licensed as per
CPU license. The Windows 2000 Advanced Server Licensing
mode on all the servers is per SEAT license.
WLBS. The web servers are connected to a Database Server
running MS SQL server enterprise edition licensed as per
CPU license. The Windows 2000 Advanced Server Licensing
mode on all the servers is per SEAT license.
Our customers are accessing our web servers and after some
time getting error 500, Maximum concurrent users have
reached.
We have been told by our software provider that the
connection problem lies with the ADO components which
communicating with the SQL server.
We have been turning round and round, without any luck.
Your help will be highly appreciated.
Thanks and best regards
Dave
Learning is a Never Ending process
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Dave Kissoondoyal (network@.bowmans.intnet.mu) writes:
> We are running three web sites in a clustered environment
> WLBS. The web servers are connected to a Database Server
> running MS SQL server enterprise edition licensed as per
> CPU license. The Windows 2000 Advanced Server Licensing
> mode on all the servers is per SEAT license.
> Our customers are accessing our web servers and after some
> time getting error 500, Maximum concurrent users have
> reached.
> We have been told by our software provider that the
> connection problem lies with the ADO components which
> communicating with the SQL server.
A message that starts with a three-digit number with a leading 5
looks like a response code from a protocol that sits on top of
TCP/IP. That is, I would assume that this message comes from the
web server and not SQL Server.
Whether the web server reacts this way due to some error code
from SQL Server, I don't know. But it seems that you will have
to investigate the web server first.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
error 500 maximum concurent users have reached
We have three Windows 2000 web servers in a WLBS environment accessing a DB server. Though we have only 180,140 and 40 connections respectively on the servers we received ERROR 500 - maximum concurent users have reached.
Please help us to identify the problem.
Best regards
Network BowmansYou may have only 300 users on the website, but the web pages themselves could be opening hordes of connections. Two things to check would be the license for SQL Server (in control panel should be a license applet for SQL Server). Check to see if you have entered 500 CALs. If you have set the server up as per-processor license, or if you have plenty of cals entered on the system, you can check in Enterprise manager to see how many connections are allowed. Right click on the server, then properties, then the connections tab. Make sure the max connections is set to 0 (unlimited). 0 is the default, and I have not had any problems with it, so far. Hope this helps.|||Hmm. After reviewing the post, I seem to have mistaken the error number for a parameter. Looks like my suggestion may not help after all. Are you certain this is a DB error, and not a web error? Check the SQL Error log to be sure.
Please help us to identify the problem.
Best regards
Network BowmansYou may have only 300 users on the website, but the web pages themselves could be opening hordes of connections. Two things to check would be the license for SQL Server (in control panel should be a license applet for SQL Server). Check to see if you have entered 500 CALs. If you have set the server up as per-processor license, or if you have plenty of cals entered on the system, you can check in Enterprise manager to see how many connections are allowed. Right click on the server, then properties, then the connections tab. Make sure the max connections is set to 0 (unlimited). 0 is the default, and I have not had any problems with it, so far. Hope this helps.|||Hmm. After reviewing the post, I seem to have mistaken the error number for a parameter. Looks like my suggestion may not help after all. Are you certain this is a DB error, and not a web error? Check the SQL Error log to be sure.
Error 4064 after attempting restore backup?!
Hi,
We have a little problem for you:
We have 2 servers both running sqlexpress2005, both have service pack 1 installed, both have the same db (same tables etc.) both have the same users with the same passwords. Everything is identical.
What I want to do is move the db. I am attempting to do this by making a backup of the db and restoring it into the second machine. (I am not sure of a more practical way to do this without stopping the SQL server).
This is the problem, the backup process works fine, without error, but when restoring the copy to the other server ,it loses the dbowner property and all default users when attempting to connect recieve a 4064 error even though all the password for users are there. Very strange.
I tried to restore the copy to to the same server that I made the copy and everything works, this only happens when attempting to restore the copy on another machine.
Do you know if this is a possible bug? I have tried to do further test on 4 different machines now and the same happens.
The objective is to be able to send the data from sqlexpress server to another by making a backup and without the need t stop the sql server. Any suggestion would be appreciated.
Adam
Even though the usernames and passwords are the same the users will have different SIDs (SQL Server's unique identifiers for users). To get a list of the orphaned users run the following on the database you restored:
EXEC sp_change_users_login 'Report'
You can then run the following command for each orphaned user to fix their relationship to the database:
EXEC sp_change_users_login 'Auto_Fix', 'user'
William, can you help me with this:
I have the same scenario as the original posting, and the orpahned user (Webuser) can be fixed with the following:
1 - EXEC sp_change_users_login 'Auto_Fix', 'webuser'
2- I must then create a table, and give webuser rights to it.
Until I do step 2 the user webuser still cannot select from any tables
How can I simplify this and allow webuser to use the db without the second step.
thanks for any help
regards
David
|||hi David,
step 1 only fixex membership to the database users... being a database user only grants (again) membership to "public" database role, and usually public members do not have lots of permissions on database objects... acutally public members do not have read/write permissions on database tables at all.. you have to manually handle that, or make the desired/required database user member of other privileged database roles, like db_datareader/db_datawriter.. or, even better, define appropriate database roles to have the desired granularity in object's permissions...
regards
|||HiSorry I did not explain adequately.
My user already has rights to all necessary tables and other objects in the db.
I am having to update a remote server with the latest version if a db, I have
no online link to that server the only possible method is manually
overwriting the mdb and ldb files
After I re-attach the updated file to the server, the user cannot select from any of those objects that they formerly had access to.
I run the sp to deal with the orphaned users issue, but then, the user still cannot select etc, even though I can look into all the object permissions and the user is shown there. So they are not an orphan, and they have explicit permissions, but they cannot see or use any of the database.
The only way I have found to resolve it is to create a new object, a table say, grant the user permissions, then hey presto suddenly they can see that, and more to the point they can see and use all the objects they are supposed to see. Then I delete the newly created table object.
The act of creating a new table and giving them rights has fixed the problem. But it cannot be the right way to do it.
regards
David
Error 4064 after attempting restore backup?!
Hi,
We have a little problem for you:
We have 2 servers both running sqlexpress2005, both have service pack 1 installed, both have the same db (same tables etc.) both have the same users with the same passwords. Everything is identical.
What I want to do is move the db. I am attempting to do this by making a backup of the db and restoring it into the second machine. (I am not sure of a more practical way to do this without stopping the SQL server).
This is the problem, the backup process works fine, without error, but when restoring the copy to the other server ,it loses the dbowner property and all default users when attempting to connect recieve a 4064 error even though all the password for users are there. Very strange.
I tried to restore the copy to to the same server that I made the copy and everything works, this only happens when attempting to restore the copy on another machine.
Do you know if this is a possible bug? I have tried to do further test on 4 different machines now and the same happens.
The objective is to be able to send the data from sqlexpress server to another by making a backup and without the need t stop the sql server. Any suggestion would be appreciated.
Adam
Even though the usernames and passwords are the same the users will have different SIDs (SQL Server's unique identifiers for users). To get a list of the orphaned users run the following on the database you restored:
EXEC sp_change_users_login 'Report'
You can then run the following command for each orphaned user to fix their relationship to the database:
EXEC sp_change_users_login 'Auto_Fix', 'user'
William, can you help me with this:
I have the same scenario as the original posting, and the orpahned user (Webuser) can be fixed with the following:
1 - EXEC sp_change_users_login 'Auto_Fix', 'webuser'
2- I must then create a table, and give webuser rights to it.
Until I do step 2 the user webuser still cannot select from any tables
How can I simplify this and allow webuser to use the db without the second step.
thanks for any help
regards
David
|||hi David,
step 1 only fixex membership to the database users... being a database user only grants (again) membership to "public" database role, and usually public members do not have lots of permissions on database objects... acutally public members do not have read/write permissions on database tables at all.. you have to manually handle that, or make the desired/required database user member of other privileged database roles, like db_datareader/db_datawriter.. or, even better, define appropriate database roles to have the desired granularity in object's permissions...
regards
|||HiSorry I did not explain adequately.
My user already has rights to all necessary tables and other objects in the db.
I am having to update a remote server with the latest version if a db, I have
no online link to that server the only possible method is manually
overwriting the mdb and ldb files
After I re-attach the updated file to the server, the user cannot select from any of those objects that they formerly had access to.
I run the sp to deal with the orphaned users issue, but then, the user still cannot select etc, even though I can look into all the object permissions and the user is shown there. So they are not an orphan, and they have explicit permissions, but they cannot see or use any of the database.
The only way I have found to resolve it is to create a new object, a table say, grant the user permissions, then hey presto suddenly they can see that, and more to the point they can see and use all the objects they are supposed to see. Then I delete the newly created table object.
The act of creating a new table and giving them rights has fixed the problem. But it cannot be the right way to do it.
regards
David
Sunday, February 26, 2012
Error 3449 SQL Server shutdown
SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.
I have had two production servers shut down this week due to Error 3449: SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Previous to the shutdown I received multiple Error 3314 & 602: Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Also, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.
I am getting the same error message except ofr the last one (, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.)
How did you solve this problem,? and why this error showing up?
Thanks
|||Alright Chaps,
There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:
http://support.microsoft.com/kb/916086
regards
Jag
Error 3449 SQL Server shutdown
SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.
I have had two production servers shut down this week due to Error 3449: SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Previous to the shutdown I received multiple Error 3314 & 602: Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Also, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.
I am getting the same error message except ofr the last one (, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.)
How did you solve this problem,? and why this error showing up?
Thanks
|||Alright Chaps,
There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:
http://support.microsoft.com/kb/916086
regards
Jag
Sunday, February 19, 2012
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
Chris
Hi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
Chris
Hi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Friday, February 17, 2012
Error 21776 when mapping orphaned users..
When restoring a database to another server (both servers running SQL Server
7) I use the sp_change_users_login procedure ("Update_one" argument) to map
one particular orphaned user to a user on the new server. This orphaned user
happens to be the dbo of the database on the original server.
The procedure exucutes correctly, but when I look in Enterprise Manager
(login properties) I get the Error 21776 message "The name "xxx" was not
found in the users collection..." etc.
Is this only a refresh problem whitin Enterprise Manager? If not, can I just
ignore it anyway, or do I have to take further actions to have it working
the way I want it to (that is, to let the user on the new server access the
restored database)
Thanks for your help!
Per WilliamsonTry to exit EM and start it again, to see if it is a refresh issue.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Per Williamson" <per.williamson@.telia.com> wrote in message
news:G5dEb.42639$dP1.166871@.newsc.telia.net...
> When restoring a database to another server (both servers running SQL Server
> 7) I use the sp_change_users_login procedure ("Update_one" argument) to map
> one particular orphaned user to a user on the new server. This orphaned user
> happens to be the dbo of the database on the original server.
> The procedure exucutes correctly, but when I look in Enterprise Manager
> (login properties) I get the Error 21776 message "The name "xxx" was not
> found in the users collection..." etc.
> Is this only a refresh problem whitin Enterprise Manager? If not, can I just
> ignore it anyway, or do I have to take further actions to have it working
> the way I want it to (that is, to let the user on the new server access the
> restored database)
> Thanks for your help!
> Per Williamson
>
7) I use the sp_change_users_login procedure ("Update_one" argument) to map
one particular orphaned user to a user on the new server. This orphaned user
happens to be the dbo of the database on the original server.
The procedure exucutes correctly, but when I look in Enterprise Manager
(login properties) I get the Error 21776 message "The name "xxx" was not
found in the users collection..." etc.
Is this only a refresh problem whitin Enterprise Manager? If not, can I just
ignore it anyway, or do I have to take further actions to have it working
the way I want it to (that is, to let the user on the new server access the
restored database)
Thanks for your help!
Per WilliamsonTry to exit EM and start it again, to see if it is a refresh issue.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Per Williamson" <per.williamson@.telia.com> wrote in message
news:G5dEb.42639$dP1.166871@.newsc.telia.net...
> When restoring a database to another server (both servers running SQL Server
> 7) I use the sp_change_users_login procedure ("Update_one" argument) to map
> one particular orphaned user to a user on the new server. This orphaned user
> happens to be the dbo of the database on the original server.
> The procedure exucutes correctly, but when I look in Enterprise Manager
> (login properties) I get the Error 21776 message "The name "xxx" was not
> found in the users collection..." etc.
> Is this only a refresh problem whitin Enterprise Manager? If not, can I just
> ignore it anyway, or do I have to take further actions to have it working
> the way I want it to (that is, to let the user on the new server access the
> restored database)
> Thanks for your help!
> Per Williamson
>
Subscribe to:
Posts (Atom)