Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts

Thursday, March 8, 2012

Cannot uninstall SQL Express 2005 Instances

Using Windows XP SQL Express 2005...

In Windows Installer Clean Up, it shows two instances:

MSSMLBIZ (used by Outlook Enterprice 07 with BCM)

Control, Panel, Add Remove, Remove SQL Express 2005, shows:

CSOLUTION (which is disabled)

MSSMLBIZ (enabled for BCM 07)

SQLEXPRESS (which is disabled)

The disabled instances will not start due to various error messages.

Under Computer, Manager, Services, more instances are listsed, which also will not start:

SQLEXPRESSDATA for example (which is disabled)

I would like to remove CSOLUTION since it is not used; it will not remove from control panel or manually via http://support.microsoft.com/default.aspx/kb/909967 . You get various error messages, such as

Another application has exclusive access to the file c:\program files\...errorlog. Please shut down all other applications, then try again.

Even after a reboot, I still get this error.

I want to install and use instance SQLExpress, and I cannot remove it, but it will not start, and trying to reinstall it fails.

It was simple under MSDE 2000, no2 it seems to be impossible.

Does anyone have any ideas?

Honestly, I would like to uninstall SQL Express 2005 completely (except the BCM instant), and start over, but canot find a way to do this. SQL Express is a mess, I have spent days trying to resolve this, and am still where I started.

Thanks, bob

Which error messages does the SQL Server Express service bring up ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

THe error message is stated in my post. If you do not get that error message, it looks like it is trying to uninstall, but then just returns to the Control panel add/remove listing the instances, with nothing removed and no further error messages.

Thanks,

Bob

Cannot uninstall SQL Express 2005 Instances

Using Windows XP SQL Express 2005...

In Windows Installer Clean Up, it shows two instances:

MSSMLBIZ (used by Outlook Enterprice 07 with BCM)

Control, Panel, Add Remove, Remove SQL Express 2005, shows:

CSOLUTION (which is disabled)

MSSMLBIZ (enabled for BCM 07)

SQLEXPRESS (which is disabled)

The disabled instances will not start due to various error messages.

Under Computer, Manager, Services, more instances are listsed, which also will not start:

SQLEXPRESSDATA for example (which is disabled)

I would like to remove CSOLUTION since it is not used; it will not remove from control panel or manually via http://support.microsoft.com/default.aspx/kb/909967 . You get various error messages, such as

Another application has exclusive access to the file c:\program files\...errorlog. Please shut down all other applications, then try again.

Even after a reboot, I still get this error.

I want to install and use instance SQLExpress, and I cannot remove it, but it will not start, and trying to reinstall it fails.

It was simple under MSDE 2000, no2 it seems to be impossible.

Does anyone have any ideas?

Honestly, I would like to uninstall SQL Express 2005 completely (except the BCM instant), and start over, but canot find a way to do this. SQL Express is a mess, I have spent days trying to resolve this, and am still where I started.

Thanks, bob

Which error messages does the SQL Server Express service bring up ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

THe error message is stated in my post. If you do not get that error message, it looks like it is trying to uninstall, but then just returns to the Control panel add/remove listing the instances, with nothing removed and no further error messages.

Thanks,

Bob

Wednesday, March 7, 2012

Cannot Subscribe Using Windows Synchronization Manager

Hi,
I'm using two instances of SQL Server 2005 Developer Edition (SP2) on the
same machine. One instance is Publisher and Distributor and the other is
Subscriber. When I try to use Windows Synchronization Manager to subscribe
to the publication, I get this error:
The SQL Server publication uses features that the current version of the
Subscriber does not support. The subscriber should be upgraded to 'Unknown
version of Microsoft SQL Server'.
Any help would be greatly appreciated,
Leila
Can you check the compatibility level of the subscription database?
Also see if you can do a simple pull subscription to see if that works.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23ESWMUCTHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I'm using two instances of SQL Server 2005 Developer Edition (SP2) on the
> same machine. One instance is Publisher and Distributor and the other is
> Subscriber. When I try to use Windows Synchronization Manager to subscribe
> to the publication, I get this error:
> The SQL Server publication uses features that the current version of the
> Subscriber does not support. The subscriber should be upgraded to 'Unknown
> version of Microsoft SQL Server'.
> Any help would be greatly appreciated,
> Leila
>
|||compatibility level is 9, pull subscription without Synchronization Manager
works!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%234mNP4DTHHA.4404@.TK2MSFTNGP03.phx.gbl...
> Can you check the compatibility level of the subscription database?
> Also see if you can do a simple pull subscription to see if that works.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23ESWMUCTHHA.1200@.TK2MSFTNGP02.phx.gbl...
>
|||Sounds like something is wrong with Windows Synchronization Manager. Can you
try from another machine?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Leila" <Leilas@.hotpop.com> wrote in message
news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
> compatibility level is 9, pull subscription without Synchronization
> Manager works!
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%234mNP4DTHHA.4404@.TK2MSFTNGP03.phx.gbl...
>
|||I'll try that!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
> Sounds like something is wrong with Windows Synchronization Manager. Can
> you try from another machine?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
>
|||I'll try that!
One more thing: BOL says that interactive conflict resolution is not
available when you synchronize via SSMS. Then why is there such an option
when you create the subscription in SSMS?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
> Sounds like something is wrong with Windows Synchronization Manager. Can
> you try from another machine?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
>
|||It is for subscriptions that you will pull through WSM. Note you have to
also enable interactive conflict resolution in WSM as well
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23w5nP4HTHHA.2124@.TK2MSFTNGP06.phx.gbl...
> I'll try that!
> One more thing: BOL says that interactive conflict resolution is not
> available when you synchronize via SSMS. Then why is there such an option
> when you create the subscription in SSMS?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
>
>

Cannot start SQLEXPRESS

I have just had to reinstall all my SQLServer instances (SQL2005 Standard, BCM2007, and SQLEXPRESS).

The first two have started fine, but I cannot get the SQLExpress instance to start. When I start in the Management Studio, the error I get is:-

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Loating Server/Instance Specified) (Microsoft SQL Server)."

Can anyone tell me what I have to do to correct this problem:?

I have looked in the Add or Remove Programs window and cannot see ANY instance relating to SQL Server Express 2005.

Hi,

First, if you have installed SQLExpress on your local machine then it should allow you to connect. If not try to configure it to allow remote connections. Following links will help you to do so.

And last, if you want to know about SQLEXpress instance, go to services in management console and there you can find if SQLExpress service is running or not and at the same location you can find the SQLExpress instance information.

Links are:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1712017&SiteID=1

http://techno-geeta.blogspot.com/2007/04/sql-server-2005-remote-connections.html

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Unfortunately, none of these suggestions can be implemented. SQLEXPRESS does NOT appear in either the Surface Area Configuration menu, nor in the Configuration Manager module in MMC.

It does appear in the services tab, but when I attempt to start it, I get the response:-

"Could not start the SQL Server (SQLEXPRESS) service on local computer. Error 3: the system cannot find the path specified."

How do I reconfigure this to allow it to work?

|||

Hi.

It seems that your SQLExpress installtion has problems. Please try to reinstall it. It may solve the problem.

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Mayur

Thanks for that information.

I tried the installation again, and all tasks completed successfully other than the last one "SQL Server Database Services" where it reported an error:-

"The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "Howto view SQL Server setup log files" and "Starting SQL Server manually"."

This repeats when I retry. When I cancel, the install process finishes, but the SQLExpress instance does not appear.

This install generated an error report that is apparently sent to Microsoft. However, this does NOT help me with getting SQLExpress to actually WORK.

How do I rectify this issue? I need to have this instance running so that I can support my clients with another package that depends upon this working.

I am including the last part of the summary installation log which may help with your examination:-

Failed to install package
Fatal error during installation.
Setting package return code to: 29503
Complete: InstallSqlAction at: 2007/5/17 14:45:10, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Skipped: InstallToolsAction.10
Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: InstallToolsAction
Skipped: Action "InstallToolsAction" was not run. Information reported during analysis:
No install request found for package: "tools", install will be skipped as a result.
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/5/17 14:45:10
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.

Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:Stick out tongueerform
Source Line Number: 3521

- Context --
sqls::HostSetupPackageInstallerSynch:Stick out tongueostCommit
sqls::HighlyAvailablePackage:Stick out tonguereInstall
led due to cancel code received from cancel source: 29539

|||

Hi,

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=175249&SiteID=17

I'm bit confused too but this may solve your problem.

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

|||

Mayur

This may have some bearing on my problem. Yesterday, because I was having problems updating SQLExpress with SP2, I decided to uninstall SQL Server entirely. However, I did NOT remove the various MSSQL* sub-directories. Could it be that SQL Express is getting confused with which of these it should instantiate? The sub-directories I have now are:-

MSSQL - containing what looks like my SQL Express databases - this was previously a MSDE2000 instance.

MSSQL.1 - containing what looks to be the SQL Standard edition databases. This has an OLAP sub-directory.

MSSQL.2 - does not contain any databases. This instance does have Reporting Services and OLAP sub-directories.

MSSQL.3 - also does not contain any databases.

MSSQL.4 - seems to be only Reporting Services.

MSSQL.5 - has some empty default databases.

Do you think that I should re-install SQL Server SE and SQL Server Express again, having removed the entire directory structure again? (clearly after backing up the databases I need - which I did do yesterday, of course).

|||

Hi,

I too think that, it would be a great solution. Also remove all SQL Client tools, SQL-XML and other tools that gets installed with SQL. There is no specific order in which you can install SQL Server's diff editions. However, I would recommend from older to newer and Express edition first before SQL SE 2005.

I guess, this will solve your problem. Smile

Mayur Tendulkar

Microsoft Student Partner

Asst. Manager: Pune User Group For Students

Tuesday, February 14, 2012

Cannot see an instance with BrowseConnect or OSQL /L

This summary is not available. Please click here to view the post.

Cannot see an instance with BrowseConnect or OSQL /L

Hi,
I have 3 instances of SQL server currently on my machine. The default
instance is MSDE 2000, I also have an SQL Express 2005 instance
\MACHINE\SQLEXPRESS and I have an instance of SQL Server 2000 Workgroup
Edition, named \MACHINE\WORKGROUP. When I execute SqlBrowseConnect or
"ListAllAvailableInstances" from SQL-DMO methods, I can see the 2005
instance and the default instance (local), but not the workgroup instance.
When I execute OSQL /L, I get the same result. I cannot see the Workgroup
Instance. I can however connect to the workgroup instance via. management
studio and can register it with SQL Server Configuration Manager.
I can connect to it via. OSQL and execute statements however, if I specify
the instance name on the command line. Any ideas on why it isn't visible?
According to connection properties in Management Studio (Server
Properties -> Connections), "allow remote connections" is switched on.
Robin
Okay, I fixed this by using the registry for local enumeration. Still, it's
a bit suprising to me that the browser won't enumerate all local instances -
or at least that there isn't a solid mechanism for doing so apart from
accessing the registry.
"Robinson" <toomuchspamhaspassed@.myinboxtoomuchtoooften.com > wrote in
message news:ego20b$g7q$1$830fa17d@.news.demon.co.uk...
> Hi,
> I have 3 instances of SQL server currently on my machine. The default
> instance is MSDE 2000, I also have an SQL Express 2005 instance
> \MACHINE\SQLEXPRESS and I have an instance of SQL Server 2000 Workgroup
> Edition, named \MACHINE\WORKGROUP. When I execute SqlBrowseConnect or
> "ListAllAvailableInstances" from SQL-DMO methods, I can see the 2005
> instance and the default instance (local), but not the workgroup instance.
> When I execute OSQL /L, I get the same result. I cannot see the Workgroup
> Instance. I can however connect to the workgroup instance via.
> management studio and can register it with SQL Server Configuration
> Manager.
> I can connect to it via. OSQL and execute statements however, if I specify
> the instance name on the command line. Any ideas on why it isn't visible?
> According to connection properties in Management Studio (Server
> Properties -> Connections), "allow remote connections" is switched on.
>
> Robin
>

Cannot save server properties on Case Sensitive instances

Hi all,

I've filled this suspect bug to Connect:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=282812

The issue is: I'm unable to save any change to server properties if instance is set to Case Sensitive collation .

The process returns an error like (translated from Spanish, so not exact message):

"Error in metadata manager. Log file extension should be .LOG. Error in metadata manager. Error setting ConfigurationSettings\Log\File configuration property.".

As far as I've tested this happens with any property you're trying to set when in CS collation.

My bypass has been to edit msmdsrv.ini file directly with Notepad, reverting CollationName to case insensitive.

Then everything goes fine.

Details:

Tested with AS 2005 SP2 Collation: Latin1_General_CS_AI Happens both with SSMS and direct scripting (as expected)

Best regards,

Jordi Rambla

Solid Quality Mentors

wenn Collation Latin1_CS and soon is, you should change in msmdsrv.ini in

<Log>

<File>msmdsrv.log</File>... </Log> to <File>msmdsrv.LOG</File>

Cannot save server properties on Case Sensitive instances

Hi all,

I've filled this suspect bug to Connect:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=282812

The issue is: I'm unable to save any change to server properties if instance is set to Case Sensitive collation .

The process returns an error like (translated from Spanish, so not exact message):

"Error in metadata manager. Log file extension should be .LOG. Error in metadata manager. Error setting ConfigurationSettings\Log\File configuration property.".

As far as I've tested this happens with any property you're trying to set when in CS collation.

My bypass has been to edit msmdsrv.ini file directly with Notepad, reverting CollationName to case insensitive.

Then everything goes fine.

Details:

Tested with AS 2005 SP2 Collation: Latin1_General_CS_AI Happens both with SSMS and direct scripting (as expected)

Best regards,

Jordi Rambla

Solid Quality Mentors

wenn Collation Latin1_CS and soon is, you should change in msmdsrv.ini in

<Log>

<File>msmdsrv.log</File>... </Log> to <File>msmdsrv.LOG</File>