Dear Friends,
I got this error:
Xpsql.cpp : error 87 from GetProxyAccount on line 604.
I use Ms Access for programming and SQL 2000 standart
version.
Can anyone explain to me ?, I event don't use proxy server
in my network.
Thanks.It's not a Proxy Server issue. The proxy account is used
when a non-sysadmin executes a xp_cmdshell. It's also the
security context used when a job owned by a non-sysadmin is
run. It sounds like you may need to set up the proxy account
yet. Take a look in books online for the extended stored
procedure xp_sqlagent_proxy_account. The help article has
links to related topics on xp_cmdshell and SQL Server Agent
properties (used by jobs).
-Sue
On Wed, 8 Oct 2003 19:08:00 -0700, "kresna rudy kurniawan"
<kresnark@.yahoo.com> wrote:
>Dear Friends,
>I got this error:
>Xpsql.cpp : error 87 from GetProxyAccount on line 604.
>I use Ms Access for programming and SQL 2000 standart
>version.
>Can anyone explain to me ?, I event don't use proxy server
>in my network.
>Thanks.sql
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Tuesday, March 27, 2012
Thursday, March 22, 2012
error 8102:cannot update identity column
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
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
Wednesday, March 7, 2012
error 3624 severity 20 SQL server was stopped often
hi~~
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>
Friday, February 17, 2012
Error 22002
Hi!
This is my first time in this fourm!
I've got SQL Server Standrad Edition version 8.00.760 (SP3) on Windows 2K. I'm logged in with my domain account, which is member of sysadmin
I get
"Autostart server agent" but following error appearred:
"Error 22002: Reg Create key ex() returened error 5:Access is denied"
when I check for Autostart MSDTC in SQL Server properties.
Why? Any ideas?
Thanks for all helpWhat accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?|||Originally posted by rnealejr
What accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?
Mssqlserver service and agent have the same local admin account.|||What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?|||Originally posted by rnealejr
What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?
Yes, they are .\Administrator. I don't know which dtc account use. I donot know where to look for this account! I 'm rather new at this job!|||Look for the distributed transaction coordinator service.|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
Local system account
Allow service to interact with desktop|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
I succeded starting this servicve automaticlly in Contral Panel, Services.
Thanks for your time and help!
This is my first time in this fourm!
I've got SQL Server Standrad Edition version 8.00.760 (SP3) on Windows 2K. I'm logged in with my domain account, which is member of sysadmin
I get
"Autostart server agent" but following error appearred:
"Error 22002: Reg Create key ex() returened error 5:Access is denied"
when I check for Autostart MSDTC in SQL Server properties.
Why? Any ideas?
Thanks for all helpWhat accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?|||Originally posted by rnealejr
What accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?
Mssqlserver service and agent have the same local admin account.|||What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?|||Originally posted by rnealejr
What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?
Yes, they are .\Administrator. I don't know which dtc account use. I donot know where to look for this account! I 'm rather new at this job!|||Look for the distributed transaction coordinator service.|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
Local system account
Allow service to interact with desktop|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
I succeded starting this servicve automaticlly in Contral Panel, Services.
Thanks for your time and help!
Error 21776 and dbo Problem
Hello:
We recently installed a SQL 2000 version of an older
application we were running. The company took our old
Paradox data and converted it at their site and gave us a
backup to restore to a new database we created on our SQL
server.
After restoring the database, we began to get Error 15023
messages relating to the user and login that the
application uses to grant access to the database. After
some research, I used query analyzer to drop the
questionable users and logins and then re-created them
without a problem. However, we were still getting errors
when trying to connect to the database using the
application.
While troubleshooting the problem, I went to look at the
properties of the sa account and the system threw up
Error 21776-The name dbo was not found in the users
collection. If I try to add a dbo user account to the
database in question, I get Error 15023. I can't drop
and re-create the users and logins because SQL is telling
me I can't do this with a database owner. I can't use
sp_change_users_login because it involves the dbo account.
I don't know where to go from here.
Any comments or suggestions would be appreciated.
Thanks
BrennanHave you checked this article?
305711 BUG: DBO User Does Not Display in Enterprise Manager
http://support.microsoft.com/?id=305711
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
We recently installed a SQL 2000 version of an older
application we were running. The company took our old
Paradox data and converted it at their site and gave us a
backup to restore to a new database we created on our SQL
server.
After restoring the database, we began to get Error 15023
messages relating to the user and login that the
application uses to grant access to the database. After
some research, I used query analyzer to drop the
questionable users and logins and then re-created them
without a problem. However, we were still getting errors
when trying to connect to the database using the
application.
While troubleshooting the problem, I went to look at the
properties of the sa account and the system threw up
Error 21776-The name dbo was not found in the users
collection. If I try to add a dbo user account to the
database in question, I get Error 15023. I can't drop
and re-create the users and logins because SQL is telling
me I can't do this with a database owner. I can't use
sp_change_users_login because it involves the dbo account.
I don't know where to go from here.
Any comments or suggestions would be appreciated.
Thanks
BrennanHave you checked this article?
305711 BUG: DBO User Does Not Display in Enterprise Manager
http://support.microsoft.com/?id=305711
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
error 21268
I have msde version 8.00.760 and when I try a sqlmaint it tells me
[Microsoft SQL-DMO] Error 21268: [SQL-DMO]Row or column specified is outside
the
range of the specified query result set.
this refers to sql 200 sp2 .. when I try upgrade to service pack 3 it tells
I do not have sql 2000 on my system
Please help
Frank
hi Frank,
frank wrote:
> I have msde version 8.00.760 and when I try a sqlmaint it tells me
8.00.760 is service pack 3
> [Microsoft SQL-DMO] Error 21268: [SQL-DMO]Row or column specified is
> outside the
> range of the specified query result set.
> this refers to sql 200 sp2 .. when I try upgrade to service pack 3 it
> tells I do not have sql 2000 on my system
>
how are you trying to upgrade to sp3 (BTW, you already have it installed...
you eventually should go for sp4)?
pleas post the command prompt line you execute including all parameters as
long as your original instance name..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
[Microsoft SQL-DMO] Error 21268: [SQL-DMO]Row or column specified is outside
the
range of the specified query result set.
this refers to sql 200 sp2 .. when I try upgrade to service pack 3 it tells
I do not have sql 2000 on my system
Please help
Frank
hi Frank,
frank wrote:
> I have msde version 8.00.760 and when I try a sqlmaint it tells me
8.00.760 is service pack 3
> [Microsoft SQL-DMO] Error 21268: [SQL-DMO]Row or column specified is
> outside the
> range of the specified query result set.
> this refers to sql 200 sp2 .. when I try upgrade to service pack 3 it
> tells I do not have sql 2000 on my system
>
how are you trying to upgrade to sp3 (BTW, you already have it installed...
you eventually should go for sp4)?
pleas post the command prompt line you execute including all parameters as
long as your original instance name..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
Wednesday, February 15, 2012
error 1937 installing sql express
Please help me!
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Sat Jul 15 12:51:21 2006
Machine : JIMMY
Product : File di supporto dell'installazione di Microsoft SQL Server (Italiano)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQLSupport_1.log
--
Machine : JIMMY
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQLNCLI_1.log
--
Machine : JIMMY
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SqlWriter_1.log
--
Machine : JIMMY
Product : Parser MSXML 6.0
Product Version : 6.00.3883.15
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_MSXML6_1.log
--
Machine : JIMMY
Product : File di supporto dell'installazione di Microsoft SQL Server (Italiano)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQLSupport_2.log
--
Machine : JIMMY
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQLNCLI_2.log
--
Machine : JIMMY
Product : Parser MSXML 6.0
Product Version : 6.00.3883.15
Install : Successful
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_MSXML6_2.log
--
Machine : JIMMY
Product : Servizi di database SQL Server
Error : Errore durante l'installazione dell'assembly 'Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Firma o catalogo non verificabili o non validi. HRESULT: 0x80131045.
--
Machine : JIMMY
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQL.log
Last Action : InstallFinalize
Error String : Errore durante l'installazione dell'assembly 'Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Firma o catalogo non verificabili o non validi. HRESULT: 0x80131045. interfaccia assembly: IAssemblyCacheItem, funzione: Commit, componente: {FD5D8A34-6302-4B57-A51D-65A834A1EF6F}
Error Number : 1937
--
Hi Agostino,
Please check the file at C:\programmi\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JIMMY_SQL.log to see if it offers additional information.
I'm moving this to the setup form so they can troubleshoot for you.
Mike
|||hi Mike,
the log above (from the file you suggested me in the previous message) tells something about the error but i can't understand. Can you help me?
Bye,
Ago
MSI (s) (44:30) [12:56:11:359]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=366409477)
MSI (s) (44:30) [12:56:11:453]: Assembly Error:Strong name signature verification failed for assembly '%1'. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.
MSI (s) (44:30) [12:56:11:468]: Note: 1: 1937 2: {FD5D8A34-6302-4B57-A51D-65A834A1EF6F} 3: 0x80131045 4: IAssemblyCacheItem 5: Commit 6: Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (44:30) [12:56:32:203]: Prodotto: Microsoft SQL Server 2005 Express Edition -- Errore 1937. Errore durante l'installazione dell'assembly 'Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Firma o catalogo non verificabili o non validi. HRESULT: 0x80131045. interfaccia assembly: IAssemblyCacheItem, funzione: Commit, componente: {FD5D8A34-6302-4B57-A51D-65A834A1EF6F}
Errore 1937. Errore durante l'installazione dell'assembly 'Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Firma o catalogo non verificabili o non validi. HRESULT: 0x80131045. interfaccia assembly: IAssemblyCacheItem, funzione: Commit, componente: {FD5D8A34-6302-4B57-A51D-65A834A1EF6F}
MSI (s) (44:30) [12:56:32:281]: User policy value 'DisableRollback' is 0
MSI (s) (44:30) [12:56:32:281]: Machine policy value 'DisableRollback' is 0
Fine operazione 12.56.32: InstallFinalize. Valore restituito 3.
Thanks,
Samuel Lester (MSFT)
Subscribe to:
Posts (Atom)