MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because
a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/arch.../13/465401.aspx
John|||Thanks.This http://blogs.msdn.com/astebner/arch.../13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/arch.../13/465401.aspx
> John
>
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Tuesday, March 20, 2012
Removing SQLServer 2005 Express Registry Keys
MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
Removing SQLServer 2005 Express Registry Keys
MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
Removing SQLServer 2005 Express Registry Keys
MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>> MS update cannot install a Service Pack to SQL Server 2005 Express
>> because a
>> component of an earlier version (a CTP, the Reporting Services component)
>> cannot be uninstalled. Can anyone tell me which set of registry keys I
>> should delete after removing SQL Server 2005 in order to reinstall on a
>> clean sustem?
>> Many thanks.
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>> MS update cannot install a Service Pack to SQL Server 2005 Express
>> because a
>> component of an earlier version (a CTP, the Reporting Services component)
>> cannot be uninstalled. Can anyone tell me which set of registry keys I
>> should delete after removing SQL Server 2005 in order to reinstall on a
>> clean sustem?
>> Many thanks.
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>
Monday, March 12, 2012
Removing protected beta files
I cannot install SQL SErver 2005 because of files still on my hard disk from beta version. These include sqlmgmprovider.dll and svrenumapi.dll. The uninstall program is no longer available. How do I get rid of whatever remains of the old beta installation so that the released version of SQL Server 2005 will install?
There are a few different threads on this, so I'm copy/pasting a couple of the best:
1. Uninstall all visible Beta components in Add/Remove Programes.
2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup*_%machinename%_Core(Local).log. * stands for a number. Check the latest log file.
3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.
4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.
5. Reboot the machine.
6. Start Setup again.
If these don't work, check out this thread using some of the zap tools:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=89919&SiteID=1
Thanks,
Sam Lester (MSFT)
|||
Thanks, Sam,
The zap tool worked and I was able to get past the objection to the old beta files. However, the install was not completely successful. In fact the main part of it did not install successfully. Do you have any hints on how to diagnose this problem?
Allen
(moontube)
|||What SKU are you trying to install and on what OS? If you're going through a command line install, can you supply the command line string? If you're going through UI, where is it failing?
Go ahead and search your install logs in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG for the text string "value 3" and then copy/paste the 10-20 or so lines above that message. This should give us a more descript error message.
Thanks,
Sam
|||
Hi Sam,
Here is the LOG information you asked for.
MSI (s) (B0:04) [22:58:52:948]: Executing op: UpgradeCodePublish(UpgradeCode={929C9FEC-8873-4A1A-A209-9AF432E8E1D1})
MSI (s) (B0:04) [22:58:52:948]: Executing op: SourceListPublish(,,DiskPromptTemplate=Please insert next disk,PackagePath=\Setup\,NumberOfDisks=1)
MSI (s) (B0:04) [22:58:52:948]: Note: 1: 1402 2: UNKNOWN\Installer\Products\1EB3A031CC585314E87AA527E46EECC2\SourceList 3: 2
MSI (s) (B0:04) [22:58:52:968]: Executing op: ProductPublishClient(,,)
MSI (s) (B0:04) [22:58:52:968]: Executing op: SourceListRegisterLastUsed(SourceProduct={130A3BE1-85CC-4135-8EA7-5A724EE6CE2C},LastUsedSource=F:\Setup\)
MSI (s) (B0:04) [22:58:52:968]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (B0:04) [22:58:52:968]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (B0:04) [22:58:52:978]: Specifed source is already in a list.
MSI (s) (B0:04) [22:58:52:978]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (B0:04) [22:58:52:978]: Machine policy value 'DisableBrowse' is 0
MSI (s) (B0:04) [22:58:52:978]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (B0:04) [22:58:52:978]: Adding new sources is allowed.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedSource to: F:\Setup\.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedType to: m.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedIndex to: 1.
MSI (s) (B0:04) [22:58:52:978]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (s) (B0:04) [22:58:52:978]: Executing op: SetTargetFolder(Folder=23\Microsoft SQL Server 2005\Configuration Tools\)
MSI (s) (B0:04) [22:58:52:978]: SHELL32::SHGetFolderPath returned: E:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (B0:04) [22:58:52:998]: Executing op: ShortcutCreate(Name=SqlSAC|SQL Server Surface Area Configuration,,,FileName=E:\Program Files\Microsoft SQL Server\90\Shared\SqlSAC.exe,,,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:038]: Verifying accessibility of file: SQL Server Surface Area Configuration.lnk
MSI (s) (B0:04) [22:58:53:178]: Executing op: ShortcutCreate(Name=SqlWtsn|SQL Server Error and Usage Reporting,,,FileName=E:\Program Files\Microsoft SQL Server\90\Shared\SqlWtsn.exe,,,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:188]: Verifying accessibility of file: SQL Server Error and Usage Reporting.lnk
MSI (s) (B0:04) [22:58:53:218]: Executing op: ShortcutCreate(Name=SqlConfM|SQL Server Configuration Manager,,,FileName=E:\WINDOWS\system32\mmc.exe,Arguments=/32 "E:\WINDOWS\system32\SQLServerManager.msc",,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:228]: Verifying accessibility of file: SQL Server Configuration Manager.lnk
MSI (s) (B0:04) [22:58:53:248]: Executing op: ActionStart(Name=Set_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Completing Commit,)
MSI (s) (B0:04) [22:58:53:609]: Executing op: CustomActionSchedule(Action=Set_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1537,Source=BinaryData,Target=Set_CommitFlag,CustomActionData=010Completing Commit500001)
MSI (s) (B0:04) [22:58:53:669]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=360632758)
MSI (s) (B0:04) [22:58:54:009]: Assembly Error:The process cannot access the file because it is being used by another process.
MSI (s) (B0:04) [22:58:54:019]: Note: 1: 1935 2: {4C466AC6-57EA-4944-A4CB-795A9E01FA61} 3: 0x80070020 4: IAssemblyCacheItem 5: Commit 6: Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"
MSI (s) (B0:04) [23:06:15:815]: Product: Microsoft SQL Server 2005 -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {4C466AC6-57EA-4944-A4CB-795A9E01FA61}
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {4C466AC6-57EA-4944-A4CB-795A9E01FA61}
MSI (s) (B0:04) [23:06:15:865]: User policy value 'DisableRollback' is 0
MSI (s) (B0:04) [23:06:15:865]: Machine policy value 'DisableRollback' is 0
Action ended 23:06:15: InstallFinalize. Return value 3.
So the error is:
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Typically this is a failure when trying to install a file to the GAC. Did you remove the beta version of SQL Native Client? That sometimes causes the problem. If you didn't remove it, can you uninstall it and try the install again?
Thanks,
Sam
Hi Sam,
Thanks. your suggestion did the trick. I unistalled the corrupted version of SQL Server that I had just installed, rebooted, and installed it again. This time it worked.
Allen
|||Great to hear and thanks for replying back! For future reference, was it the SQL Native Client uninstall that fixed it for you?Thanks,
Sam|||
Hi Sam,
I uninstalled everything related it SQL Server, including the Native Client. The only thing I didn't unistall is the books, because I could not uninstall them once SQL Server had been uninstalled.
Allen
Removing protected beta files
I cannot install SQL SErver 2005 because of files still on my hard disk from beta version. These include sqlmgmprovider.dll and svrenumapi.dll. The uninstall program is no longer available. How do I get rid of whatever remains of the old beta installation so that the released version of SQL Server 2005 will install?
There are a few different threads on this, so I'm copy/pasting a couple of the best:
1. Uninstall all visible Beta components in Add/Remove Programes.
2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup*_%machinename%_Core(Local).log. * stands for a number. Check the latest log file.
3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.
4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.
5. Reboot the machine.
6. Start Setup again.
If these don't work, check out this thread using some of the zap tools:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=89919&SiteID=1
Thanks,
Sam Lester (MSFT)
Thanks, Sam,
The zap tool worked and I was able to get past the objection to the old beta files. However, the install was not completely successful. In fact the main part of it did not install successfully. Do you have any hints on how to diagnose this problem?
Allen
(moontube)
|||What SKU are you trying to install and on what OS? If you're going through a command line install, can you supply the command line string? If you're going through UI, where is it failing?
Go ahead and search your install logs in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG for the text string "value 3" and then copy/paste the 10-20 or so lines above that message. This should give us a more descript error message.
Thanks,
Sam
Hi Sam,
Here is the LOG information you asked for.
MSI (s) (B0:04) [22:58:52:948]: Executing op: UpgradeCodePublish(UpgradeCode={929C9FEC-8873-4A1A-A209-9AF432E8E1D1})
MSI (s) (B0:04) [22:58:52:948]: Executing op: SourceListPublish(,,DiskPromptTemplate=Please insert next disk,PackagePath=\Setup\,NumberOfDisks=1)
MSI (s) (B0:04) [22:58:52:948]: Note: 1: 1402 2: UNKNOWN\Installer\Products\1EB3A031CC585314E87AA527E46EECC2\SourceList 3: 2
MSI (s) (B0:04) [22:58:52:968]: Executing op: ProductPublishClient(,,)
MSI (s) (B0:04) [22:58:52:968]: Executing op: SourceListRegisterLastUsed(SourceProduct={130A3BE1-85CC-4135-8EA7-5A724EE6CE2C},LastUsedSource=F:\Setup\)
MSI (s) (B0:04) [22:58:52:968]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (B0:04) [22:58:52:968]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (B0:04) [22:58:52:978]: Specifed source is already in a list.
MSI (s) (B0:04) [22:58:52:978]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (B0:04) [22:58:52:978]: Machine policy value 'DisableBrowse' is 0
MSI (s) (B0:04) [22:58:52:978]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (B0:04) [22:58:52:978]: Adding new sources is allowed.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedSource to: F:\Setup\.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedType to: m.
MSI (s) (B0:04) [22:58:52:978]: Set LastUsedIndex to: 1.
MSI (s) (B0:04) [22:58:52:978]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (s) (B0:04) [22:58:52:978]: Executing op: SetTargetFolder(Folder=23\Microsoft SQL Server 2005\Configuration Tools\)
MSI (s) (B0:04) [22:58:52:978]: SHELL32::SHGetFolderPath returned: E:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (B0:04) [22:58:52:998]: Executing op: ShortcutCreate(Name=SqlSAC|SQL Server Surface Area Configuration,,,FileName=E:\Program Files\Microsoft SQL Server\90\Shared\SqlSAC.exe,,,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:038]: Verifying accessibility of file: SQL Server Surface Area Configuration.lnk
MSI (s) (B0:04) [22:58:53:178]: Executing op: ShortcutCreate(Name=SqlWtsn|SQL Server Error and Usage Reporting,,,FileName=E:\Program Files\Microsoft SQL Server\90\Shared\SqlWtsn.exe,,,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:188]: Verifying accessibility of file: SQL Server Error and Usage Reporting.lnk
MSI (s) (B0:04) [22:58:53:218]: Executing op: ShortcutCreate(Name=SqlConfM|SQL Server Configuration Manager,,,FileName=E:\WINDOWS\system32\mmc.exe,Arguments=/32 "E:\WINDOWS\system32\SQLServerManager.msc",,,,,ShowCmd=1,)
MSI (s) (B0:04) [22:58:53:228]: Verifying accessibility of file: SQL Server Configuration Manager.lnk
MSI (s) (B0:04) [22:58:53:248]: Executing op: ActionStart(Name=Set_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Completing Commit,)
MSI (s) (B0:04) [22:58:53:609]: Executing op: CustomActionSchedule(Action=Set_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1537,Source=BinaryData,Target=Set_CommitFlag,CustomActionData=010Completing Commit500001)
MSI (s) (B0:04) [22:58:53:669]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=360632758)
MSI (s) (B0:04) [22:58:54:009]: Assembly Error:The process cannot access the file because it is being used by another process.
MSI (s) (B0:04) [22:58:54:019]: Note: 1: 1935 2: {4C466AC6-57EA-4944-A4CB-795A9E01FA61} 3: 0x80070020 4: IAssemblyCacheItem 5: Commit 6: Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"
MSI (s) (B0:04) [23:06:15:815]: Product: Microsoft SQL Server 2005 -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {4C466AC6-57EA-4944-A4CB-795A9E01FA61}
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {4C466AC6-57EA-4944-A4CB-795A9E01FA61}
MSI (s) (B0:04) [23:06:15:865]: User policy value 'DisableRollback' is 0
MSI (s) (B0:04) [23:06:15:865]: Machine policy value 'DisableRollback' is 0
Action ended 23:06:15: InstallFinalize. Return value 3.
So the error is:
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.Replication,Typically this is a failure when trying to install a file to the GAC. Did you remove the beta version of SQL Native Client? That sometimes causes the problem. If you didn't remove it, can you uninstall it and try the install again?
Thanks,
Sam
Hi Sam,
Thanks. your suggestion did the trick. I unistalled the corrupted version of SQL Server that I had just installed, rebooted, and installed it again. This time it worked.
Allen
|||Great to hear and thanks for replying back! For future reference, was it the SQL Native Client uninstall that fixed it for you?Thanks,
Sam|||
Hi Sam,
I uninstalled everything related it SQL Server, including the Native Client. The only thing I didn't unistall is the books, because I could not uninstall them once SQL Server had been uninstalled.
Allen
Saturday, February 25, 2012
Removing Data Base Size Restriction
About a month ago I restored a data base that had been originally created in MSDE into a full version of SQL Server 2000. I thought that the size restriction would automatically be removed by putting it into the full version of SQL. I was wrong and about a week or so later the data base reached the 2GB size and needed attention. I received some assistance through Microsoft and they walked my client through the process of removing the size restriction. Since then everything has been OK.
Now I am doing something similar. My client has a data base that was originally created in MSDE. We upgraded them to SQL Express and the data base has now grown to 4GB which is the max that SQL Express allows.
We will be installing SQL for Workgroups this week.
My question is this. Is there a setting I must change inside the data base or in SQL for Workgroups that will allow the data base to grow beyond 4GB? We need to let it expand to whatever they need and I cant seem to find any documentation on whether or not I have to change a setting for this data base.
Thanks for your help. Jean
It's possible that you may need to change the autogrowth settings for the database. In Management Studio, right click the database, choose Properties, then go to the Files page. Check what's in the Autogrowth column for each file and verify that it's either set to "unrestricted growth", or restricted to a sufficiently large size. Looking at an Express Edition installation, it doesn't appear that a 4 GB autogrowth limit is selected by default, however. You should be able to load Developer Edition onto a test machine and play around with this a bit before you go live.|||Thank you David. I will take a look at that when we upgrade the customer. I am certain that is where I will find the settings. I appreciate your help. JeanMonday, February 20, 2012
Removing a Server Name
SQL
Upgrading to VS05 Pro SP1/SqlExpress (from VS03 Pro/SQL MSDE)
Question 1) – is there a way to tell which version of the SQL Express was installed?I think it is “SQL Server 2005 Express Edition With Advance Services”, but don’t know how to confirm that.
Question 2) - SQL Server Management Studio Express, Registered Servers, it shows :
Database Engine
\sqlexpress (note the lower case)
If I right click and choose “Previously Registered Servers”, it shows a message that I will be displaying SQL Server 2000 (i.e. MSDE) server names, and it shows
SQL Server Group
\SQLEXPRESS (note the upper case)
\CSOLUTION
I wish to completely remove\CSOLUTION (in MSDE you would uninstall it from the Control Panel), but right clicking and choosing the delete option does nothing (it does not delete it).Deleting SQL Server Group also has no affect either. How do I remove \CSOLUTION ?
Question 3) - In the VS05 program, the SQL connection string includes “Data Source=.\SQLEXPRESS….” (NOTE UPPER CASE)Why do I have a lower case and an upper case listed above?Starting/stopping one sqlexpress/ SQLEXPRESS does the same to the other.Don’t I wan’t to complete delete anything under SQL Server Group since it represents SQL Server 2000 (i.e. MSDE) server names?SQL Server 2000 and \CSOLUTION have been uninstalled from this machine.
Thanks!
bob
hi Bob,
BobInIndy wrote:
SQL
Upgrading to VS05 Pro SP1/SqlExpress (from VS03 Pro/SQL MSDE)
Question 1) – is there a way to tell which version of the SQL Express was installed? I think it is “SQL Server 2005 Express Edition With Advance Services”, but don’t know how to confirm that.
executing
SELECT SERVERPROPERTY('Edition'); --< will return Express Edition with Advanced Services --< where a "standard" SQLExpress instance returns Express Edition
Question 2) - SQL Server Management Studio Express, Registered Servers, it shows :
Database Engine
\sqlexpress (note the lower case)
If I right click and choose “Previously Registered Servers”, it shows a message that I will be displaying SQL Server 2000 (i.e. MSDE) server names, and it shows
SQL Server Group
\SQLEXPRESS (note the upper case)
\CSOLUTION
I wish to completely remove \CSOLUTION (in MSDE you would uninstall it from the Control Panel), but right clicking and choosing the delete option does nothing (it does not delete it). Deleting SQL Server Group also has no affect either. How do I remove \CSOLUTION ?
you usually uninstall an instance accessing the control panel Add/Remove applet...
as last resource you can manually delete it as described in http://support.microsoft.com/kb/290991/en-us
Question 3) - In the VS05 program, the SQL connection string includes “Data Source=.\SQLEXPRESS….” (NOTE UPPER CASE) Why do I have a lower case and an upper case listed above? Starting/stopping one sqlexpress/ SQLEXPRESS does the same to the other. Don’t I wan’t to complete delete anything under SQL Server Group since it represents SQL Server 2000 (i.e. MSDE) server names? SQL Server 2000 and \CSOLUTION have been uninstalled from this machine.
Thanks!
bob
the upper/lower case is not actually a problem...
regards
Subscribe to:
Posts (Atom)