Thursday, March 22, 2012
error 8102:cannot update identity column
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
Error 8102, Cannot update identity
I have setup unidirectional transaction replication between two SQL2k
servers. On the subscription database I have set the PK as (Indentity not
for Replication).
I can insert and delete records on the publisher and they get replicated
without any errors, but on the updates I get an error.
The issue I belieive is with the generated sp_MSupd stored procedure. For
some reason it is tring to execute the first block even if the logic is
false.
Can someone please advise how to get around this issue.
Thanks
This problem is caused by updating the PK. You have to look at exactly what
the application which is modifying the data on the publisher is doing.
For some applications (including ones using the .net DataGrid component),
any update of any column in a table results in the update of all columns.
This is translated as a delete followed by an insert.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:%23lUTk14mEHA.1296@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have setup unidirectional transaction replication between two SQL2k
> servers. On the subscription database I have set the PK as (Indentity not
> for Replication).
> I can insert and delete records on the publisher and they get replicated
> without any errors, but on the updates I get an error.
> The issue I belieive is with the generated sp_MSupd stored procedure. For
> some reason it is tring to execute the first block even if the logic is
> false.
> Can someone please advise how to get around this issue.
> Thanks
>
>
Wednesday, March 21, 2012
Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
I try to setup a linked server connection to an other SQL Server and receive
the following error message:
Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBInitialize::Initialize
returned 0x80004005: ].
I am using a trusted connection.
Does anybody have an idea what I am doing wrong here? Or how I can get a
more specific error message?
Thanks for any hints!
brgds,
tom.Hi Thomas:
Please see the KB article, it may be useful:
http://support.microsoft.com/defaul...kb;en-us;314530
Best Wishes
Wei Ci Zhou
Monday, March 19, 2012
error 7102
the following error during when the snapshot runs:
Error: 7102, Severity: 20, State: 7
SQL Server Internal Error. Text manager cannot continue
with current statement..
The only KB article I can find does not seem to be
relevent.
Anyone have any idea? Thanks!
Dave
Dave,
interesting - I've never heard of this error before, apart from with SQL 7.0
(http://support.microsoft.com/default...;EN-US;q246775).
A workaround in this case was to lock down the table (HOLDLOCK), but my
understanding is that the table is locked down in the snapshot creation for
merge, (unlike transactional where there is an option for concurrent
snapshot generation). You could try generating the snapshot when noone else
is on the system just to verify if it is a concurrency issue. Alternatively,
as this is apparently a new error, and assuming you have sp3 on the
publisher, distributor and subscriber, I'd consider raising this issue with
PSS.
Regards,
Paul Ibison
|||Thanks Paul,
That is kind of what I was expecting. I am the only user
connected to the database. I even tried to remove the
publication both in Enterprise manager and through the
query analyzer and I get the same error. This database
is really a copy of the original and could easily be
recreated if I could just get rid of everything.
Dave
>--Original Message--
>Dave,
>interesting - I've never heard of this error before,
apart from with SQL 7.0
>(http://support.microsoft.com/default.aspx?scid=kb;EN-
US;q246775).
>A workaround in this case was to lock down the table
(HOLDLOCK), but my
>understanding is that the table is locked down in the
snapshot creation for
>merge, (unlike transactional where there is an option
for concurrent
>snapshot generation). You could try generating the
snapshot when noone else
>is on the system just to verify if it is a concurrency
issue. Alternatively,
>as this is apparently a new error, and assuming you have
sp3 on the
>publisher, distributor and subscriber, I'd consider
raising this issue with
>PSS.
>Regards,
>Paul Ibison
>
>.
>
Error 70038 on install Solved!
Hi all
I packaged .Net Framework & Sql Express with my setup project. When I attempt to install it on an XP (with SP2) system .Net Framework installs fine. The Sql Express gets about 25% of the way through then fails. Here's the content of the log file:
The following properties have been set:
Property: [AdminUser] = true {boolean}
Property: [ProcessorArchitecture] = Intel {string}
Property: [VersionNT] = 5.1.2 {version}
Running checks for package '.NET Framework 2.0', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\dotnetfx\dotnetchk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'DotNetInstalled'
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\Internet Explorer'
Read string value '6.0.2900.2180'
Setting value '6.0.2900.2180 {string}' for property 'IEVersion'
The following properties have been set for package '.NET Framework 2.0':
Property: [DotNetInstalled] = 1 {int}
Property: [IEVersion] = 6.0.2900.2180 {string}
Running checks for command 'dotnetfx\instmsia.exe'
Result of running operator 'ValueExists' on property 'VersionNT': true
Result of checks for command 'dotnetfx\instmsia.exe' is 'Bypass'
Running checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe'
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.0.3': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.0': true
Result of checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
Running checks for command 'dotnetfx\dotnetfx.exe'
Result of running operator 'ValueNotEqualTo' on property 'DotNetInstalled' and value '0': true
Result of checks for command 'dotnetfx\dotnetfx.exe' is 'Bypass'
'.NET Framework 2.0' RunCheck result: No Install Needed
Running checks for package 'SQL Server 2005 Express Edition', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
EULA for components 'SQL Server 2005 Express Edition' was accepted.
Copying files to temporary directory "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\"
Copying from '\\.host\Shared Folders\G-CDRW\MovieCollection Setup\Debug\SqlExpress\sqlexpr32.exe' to 'C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe'
Running checks for package 'SQL Server 2005 Express Edition', phase BeforePackage
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
Verifying file integrity of C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe
WinVerifyTrust returned 0
File trusted
Installing using command line '"C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe" -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SQLAUTOSTART=1'
Process exited with code 70038
Status of package 'SQL Server 2005 Express Edition' after install is 'InstallFailed'
--
Any ideas?
TIA
Gary
Hi Gary,
I got the same error today on my Win XP SP2 workstation. An update for the MSI installer to Version 3.1 helped. After that, SQLexpress could be installed correctly.
Have a nice day
Ralf.
|||Hi RalfThanks for your posting. Works beautifully!
Gary|||
I also got the same error,
I see in the log
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
In the package.xml file it states that:
<BypassIf Property="VersionNT" Compare="VersionGreaterThanOrEqualTo" Value="5.1"/>
Should this be there? Why would we bypass sql installation if VersionNT is >= 5.1?
Error 70038 on install Solved!
Hi all
I packaged .Net Framework & Sql Express with my setup project. When I attempt to install it on an XP (with SP2) system .Net Framework installs fine. The Sql Express gets about 25% of the way through then fails. Here's the content of the log file:
The following properties have been set:
Property: [AdminUser] = true {boolean}
Property: [ProcessorArchitecture] = Intel {string}
Property: [VersionNT] = 5.1.2 {version}
Running checks for package '.NET Framework 2.0', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\dotnetfx\dotnetchk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'DotNetInstalled'
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\Internet Explorer'
Read string value '6.0.2900.2180'
Setting value '6.0.2900.2180 {string}' for property 'IEVersion'
The following properties have been set for package '.NET Framework 2.0':
Property: [DotNetInstalled] = 1 {int}
Property: [IEVersion] = 6.0.2900.2180 {string}
Running checks for command 'dotnetfx\instmsia.exe'
Result of running operator 'ValueExists' on property 'VersionNT': true
Result of checks for command 'dotnetfx\instmsia.exe' is 'Bypass'
Running checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe'
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.0.3': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.0': true
Result of checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
Running checks for command 'dotnetfx\dotnetfx.exe'
Result of running operator 'ValueNotEqualTo' on property 'DotNetInstalled' and value '0': true
Result of checks for command 'dotnetfx\dotnetfx.exe' is 'Bypass'
'.NET Framework 2.0' RunCheck result: No Install Needed
Running checks for package 'SQL Server 2005 Express Edition', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
EULA for components 'SQL Server 2005 Express Edition' was accepted.
Copying files to temporary directory "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\"
Copying from '\\.host\Shared Folders\G-CDRW\MovieCollection Setup\Debug\SqlExpress\sqlexpr32.exe' to 'C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe'
Running checks for package 'SQL Server 2005 Express Edition', phase BeforePackage
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
Verifying file integrity of C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe
WinVerifyTrust returned 0
File trusted
Installing using command line '"C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe" -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SQLAUTOSTART=1'
Process exited with code 70038
Status of package 'SQL Server 2005 Express Edition' after install is 'InstallFailed'
--
Any ideas?
TIA
Gary
Hi Gary,
I got the same error today on my Win XP SP2 workstation. An update for the MSI installer to Version 3.1 helped. After that, SQLexpress could be installed correctly.
Have a nice day
Ralf.
|||Hi RalfThanks for your posting. Works beautifully!
Gary|||
I also got the same error,
I see in the log
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
In the package.xml file it states that:
<BypassIf Property="VersionNT" Compare="VersionGreaterThanOrEqualTo" Value="5.1"/>
Should this be there? Why would we bypass sql installation if VersionNT is >= 5.1?
Error 70038 on install
Hi all
I packaged .Net Framework & Sql Express with my setup project. When I attempt to install it on an XP (with SP2) system .Net Framework installs fine. The Sql Express gets about 25% of the way through then fails. Here's the content of the log file:
The following properties have been set:
Property: [AdminUser] = true {boolean}
Property: [ProcessorArchitecture] = Intel {string}
Property: [VersionNT] = 5.1.2 {version}
Running checks for package '.NET Framework 2.0', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\dotnetfx\dotnetchk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'DotNetInstalled'
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\Internet Explorer'
Read string value '6.0.2900.2180'
Setting value '6.0.2900.2180 {string}' for property 'IEVersion'
The following properties have been set for package '.NET Framework 2.0':
Property: [DotNetInstalled] = 1 {int}
Property: [IEVersion] = 6.0.2900.2180 {string}
Running checks for command 'dotnetfx\instmsia.exe'
Result of running operator 'ValueExists' on property 'VersionNT': true
Result of checks for command 'dotnetfx\instmsia.exe' is 'Bypass'
Running checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe'
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.0.3': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.0': true
Result of checks for command 'dotnetfx\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
Running checks for command 'dotnetfx\dotnetfx.exe'
Result of running operator 'ValueNotEqualTo' on property 'DotNetInstalled' and value '0': true
Result of checks for command 'dotnetfx\dotnetfx.exe' is 'Bypass'
'.NET Framework 2.0' RunCheck result: No Install Needed
Running checks for package 'SQL Server 2005 Express Edition', phase BuildList
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
EULA for components 'SQL Server 2005 Express Edition' was accepted.
Copying files to temporary directory "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\"
Copying from '\\.host\Shared Folders\G-CDRW\MovieCollection Setup\Debug\SqlExpress\sqlexpr32.exe' to 'C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe'
Running checks for package 'SQL Server 2005 Express Edition', phase BeforePackage
Running external check with command line "C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\SqlExpressChk.exe"
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressInstalled'
The following properties have been set for package 'SQL Server 2005 Express Edition':
Property: [SQLExpressInstalled] = 1 {int}
Running checks for command 'SqlExpress\sqlexpr32.exe'
Result of running operator 'ValueEqualTo' on property 'SQLExpressInstalled' and value '0': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueExists' on property 'Version9x': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': false
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Install'
'SQL Server 2005 Express Edition' RunCheck result: Install Needed
Verifying file integrity of C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe
WinVerifyTrust returned 0
File trusted
Installing using command line '"C:\DOCUME~1\Gary\LOCALS~1\Temp\VSDA0.tmp\SqlExpress\sqlexpr32.exe" -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SQLAUTOSTART=1'
Process exited with code 70038
Status of package 'SQL Server 2005 Express Edition' after install is 'InstallFailed'
--
Any ideas?
TIA
Gary
Hi Gary,
I got the same error today on my Win XP SP2 workstation. An update for the MSI installer to Version 3.1 helped. After that, SQLexpress could be installed correctly.
Have a nice day
Ralf.
|||Hi RalfThanks for your posting. Works beautifully!
Gary|||
I also got the same error,
I see in the log
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionNT' and value '5.1': true
Result of checks for command 'SqlExpress\sqlexpr32.exe' is 'Bypass'
Running checks for command 'SqlExpress\sqlexpr32.exe'
In the package.xml file it states that:
<BypassIf Property="VersionNT" Compare="VersionGreaterThanOrEqualTo" Value="5.1"/>
Should this be there? Why would we bypass sql installation if VersionNT is >= 5.1?
Friday, February 24, 2012
Error 29506. SQL Server Setup failed to modify security permissions
MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
Tried running install with a domain account and local account with same results.
Based on the error message, I checked permission on the drive and still received the same error.
Followed resolution based on KB 916766, this did not resolve the error.
Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.
Many Thanks
http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions
|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL
Error 29506. SQL Server Setup failed to modify security permissions
MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
Tried running install with a domain account and local account with same results.
Based on the error message, I checked permission on the drive and still received the same error.
Followed resolution based on KB 916766, this did not resolve the error.
Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.
Many Thanks
http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions
|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL
Sunday, February 19, 2012
Error 22029 on maint jobs
I have a SQL server 2000 on Windows Server 2003.
I have setup a Maint plan that backs up the user and system databases
and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well.
I am not attempting to repair any minor problems.
I am not performing integrity checks before backing up the database
and transaction logs.
All of the databases that I am doing a transaction log backup on have
recovery mode of full.
When the jobs run they fail instantly with error code 22029.
Sqlmaint.exe failed to run. This was working up until the end of the
day on the Thursday before Good Friday. (last week) The transaction
log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No
changes were made to the server during that time.
Another issue that started at the same time. I have a web page used to
grab data from a text file export and pull it into an AS400. I use
this server to house the DTS packages and stored procedures that the
process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server
and most others still in a NT 4 domain. We have been like this for at
least 3 months and everything has worked fine. I setup the various
users and systems the way the need to be, to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with
local administrator rights to the local box and server role of system
administrator. The MSSQLSERVER and DTC services were running as the
built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then
after a period of time that I have not figured out yet, but more than
15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL
system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account.
Still same thing.
I run the sqlmaint from command line with the switches that I am using
in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine
from with in Query analyzer.
Any help you can provide would be greatly appreciated.
Hi
I don′t know i this might help, but we experienced the exact same symptoms. And it started around the date you mentioned.
In our case we had a job that made a backup of 'All databases'. However we had 2 detached databases on our server, when I deleted those the job ran without errors!
Good luck
Friday, February 17, 2012
Error 22022
was setup to use 2 separate local accounts as recommended by MS best
practices. I also have a similar configuration on my LAO that uses 2 domain
accounts. None of the accounts are local admins. The domain SQL server
works perfectly. The DMZ SQL server will not run with 2 accounts - I get
the famous errors, 22022, 15401, and 17052. I have found many articles on
users with the same problem and that to fix the error the accounts must be
local admins or just use one account. I have gotten around the problem by
just using one account but can anyone explain why it works in the domain
with 2 accounts but not in a workgroup'
Thanks for any insight.Hi Bad,
Welcome.
From your description, one of the SQL Server which is setup to use two
accounts not work in your environment. Also if changed to single acount, it
works. For the two accounts, I'm not quite sure which two account setting
is SQL Server are the ones you mentioned. Are they the SQLServer db
service's running account or sql agent's account? If convenient, would you
please attach a screenshot of the two account configuration so that we can
get a clear view?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||One account starts the MS SSQL service and one account is used for the SQL
agent.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:6mOZgPxJGHA.3680@.TK2MSFTNGXA02.phx.gbl...
> Hi Bad,
> Welcome.
> From your description, one of the SQL Server which is setup to use two
> accounts not work in your environment. Also if changed to single acount,
> it
> works. For the two accounts, I'm not quite sure which two account setting
> is SQL Server are the ones you mentioned. Are they the SQLServer db
> service's running account or sql agent's account? If convenient, would
> you
> please attach a screenshot of the two account configuration so that we can
> get a clear view?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Hi Bad,
Thanks for your followup.
I've also checked the error code you posted and it seems those error code
are specific to the SQL Mail which runs in the SQL Agent service.
Therefore, I think the problem here should be the account of the SQL Agent
service is not quite sufficient for performing all the tasks. And when you
change it to use the same account as the SQLServer database service's
account , it works (which pretend to indicate that we should configure them
to the same account), however, actually different accounts with sufficient
permission should also work.
Anyway, I think we may perform some further test on the SQL Agent's
security setting. For the problem SQL Agent account, I suggest you try
adding it into SQLServer's security logins and grant it SA role and restart
the SQL agent service to see whether it helps.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Error 21074: Subscriptions being made inactive
In my Single subscriber setup with Transactional Replication, i have
received this error on Distribution agent:
"The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be dropped and
recreated."
I know that this error occurs when the pull agent is unable to
transfer transactions to the Subscriber and the distribution DB is
piling up with transactions. And this happens for more than 48hrs
(default).
1. Can someone help in finding the possible reasons for my
distribution DB not running?
Am unable to see any errors, since all my log entries in the
Distribution Agent History have got cleaned because this issue occured
some one month back. All maintenance agents are run at default
settings.
2. As a solution, i just made the subscription status to Active by
running the below query:
update distribution..MSsubscriptions set status=2 where
publisher_id='x' and
publisher_db='x' and publication_id='x' and subscriber_id='x' and
subscriber_db='x'
However, the transactions which were run between subscription turning
from inactive to Active does not get synchronised. This causes some of
them to be lost. And only new transactions from the time it is made
active are being sent. Is this by design or changeable?
Please help me asap.
Thanks in advance,
Lavanya
On Apr 3, 12:07 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> Have a look at the schedule of the distribution agent on the subscriber. If
> it's on demand then this is quite understandable and setting the transaction
> retention period, the history retention period and the publication's
> reinitialization period all to a suitably high value will prevent this
> occurring next time.
> At this stage you'll need to reinitialize rather than try to fix the status,
> as some commands might have been cleaned-up so there could be
> non-convergence occurring.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com
Thanks Paul.
Distribution agents run continuously from all publishers to this
centralized subscriber.
Due to some reason, the distribution agent was in retrying state for
more than the transaction retention period and hence the subscription
got marked as inacive.
Does History retention period cause subscription to become inactive?
Hope it does not.
Another clarification is whether setting transaction retention period
as 365 days, how do i measure/expect the transactional replication
performance to be affected? I use multiple publishers and a
centralised subscriber.
|||On Apr 3, 11:57 pm, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> The History retention period needs to be set to be consistant with the
> transaction retention period.
> If the retention period is set to be 1 year, the distribution database can
> balloon up and the distribution agent can take progressively longer finding
> the commands to be sent to the subscriber.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com
Let me know what do you mean by maintaining the history retention
period as consistent.
Can i set something like this? Will this have an impact on
performance?
History retention = 100 hours
Transaction retention = 72 hours.
Also, Does History retention period cause subscription to become
inactive?
Thanks,
Lavanya