Problem restoring SQL Svr 2000 Master db - wrong server version?

I'm trying to rebuild from a meltdown. I'm using disk backup files. I
could have sworn that I had SQL Server 2000 SP3 installed on the old
machine, but maybe not.

With SP3 installed, I get a message along the lines that the restore
can't be done because the backup was created using server version
134218262 and this server is version 134218488.

I've searched the documentation and can't find any reference to those
version numbers.

In any case, I thought SQL Server 2000 could restore backups created
on any SP level to any SP level.

Any ideas?

--
Regards.
Richard.On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
<richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:

>I'm trying to rebuild from a meltdown. I'm using disk backup files. I
>could have sworn that I had SQL Server 2000 SP3 installed on the old
>machine, but maybe not.

Ooop. Sorry. I had SP2 installed.

--
Regards.
Richard.|||"Richard Sherratt" <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote in
message news:dp7700dtggi3ev97mmgfgtacct926mjdb4@.4ax.com...
> On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
> <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:
> >I'm trying to rebuild from a meltdown. I'm using disk backup files. I
> >could have sworn that I had SQL Server 2000 SP3 installed on the old
> >machine, but maybe not.
> Ooop. Sorry. I had SP2 installed.

You mention the master DB in the subject.

I believe the system databases (Master, Model, MSDB) have to be restored to
the same level service pack they were backed up from.

Otherwise you're right. You can restore different SP levels of dbs to
different servers.

>
> --
> Regards.
> Richard.|||"Greg D. Moore \(Strider\)" <mooregr@.greenms.com> wrote in message news:<eRSMb.72883$Dq1.66308@.twister.nyroc.rr.com>...
> "Richard Sherratt" <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote in
> message news:dp7700dtggi3ev97mmgfgtacct926mjdb4@.4ax.com...
> > On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
> > <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:
> > >I'm trying to rebuild from a meltdown. I'm using disk backup files. I
> > >could have sworn that I had SQL Server 2000 SP3 installed on the old
> > >machine, but maybe not.
> > Ooop. Sorry. I had SP2 installed.
> You mention the master DB in the subject.
> I believe the system databases (Master, Model, MSDB) have to be restored to
> the same level service pack they were backed up from.
> Otherwise you're right. You can restore different SP levels of dbs to
> different servers.

As part of a D&R test we restored databases to new servers, much the
same as you appear to be trying.

My best guess is that you have a different server name. We made sure
that the servers had the same name as the 'real' ones. If you are
dealing with a meltdown, this might actually help because your client
software won't have to be modified for the new server name.
>
> > --
> > Regards.
> > Richard.|||On Tue, 13 Jan 2004 13:59:38 GMT, "Greg D. Moore \(Strider\)"
<mooregr@.greenms.com> wrote:

<snip
>You mention the master DB in the subject.
>I believe the system databases (Master, Model, MSDB) have to be restored to
>the same level service pack they were backed up from.
>Otherwise you're right. You can restore different SP levels of dbs to
>different servers.

Thanks. That would explain it.

--
Regards.
Richard.

Problem installing SQL Server 2005 Express with Advance Services CTP

Hi,

I was unable to install the CTP version of SS Express Edition SP1 with Advance Services. The installation failed with the following error message:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

However, I was able to install and run the standard CTP version of SS Express Edition SP1 without any problems, even though the above error message indicated I may have login problem. First let me confess that my computer does not have IIS installed, which as I understand is only needed for running the Report Services. Is it necessary for IIS to be up and running while installing SSEE with Advance Services?

The main reason I want to install SSEE with Advance Services is to use the full text search capability. I do not need the Report Services, and was hoping there is an option to turn it off and not require IIS. Is this possible?

Mike

Hi Mike,

You do not need to have IIS installed or running to install Express Advanced as long as you don't need Reporting Services. As far as the error you're getting, we'd really need to check for additional informaiton in the setup log. Could you check that out and get back to the thread with the info from the log?

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Hi Mike,

I am glad to hear that IIS is not required for SQLExpress Advanced installation. The error I got is as follows taken from the summary log file.

Machine : WS2
Product : Microsoft SQL Server 2005
Product Version : 9.1.2040.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_WS2_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error Number : 29515

Background information: (OS: Windows XP SP2)

1. Logged in as user with local administrative priviliges.

2. Installed SQL Express RTM a while back, and was able to login to instance and use databases.

3. Attempted to install SQLExpress Advanced CTP without uninstalling SQLExpress RTM. This process is suppose to upgrade the existing installation.

4. *** Installation fails and the sql server setup installation rolls back. *** The previous installation (SQLExpress RTM) is automatically restored, and I am able to login to the sql server.

5. l then try to install SQLExpress CTP. This works perfectly. Note I did not make any changes between steps 4 and 5 (e.g. no reboot, etc.).

Looking through the log files it looks like the SQLExpress Advanced is trying to make an ODBC connection and failing. Why is it trying to use ODBC?

Anyway there is a lot of information in the logs that I do not understand, so it would be better if I could send them to you. (All the log files are in a 1.3M cab file) Please advise.

Thanks,

Mike

|||I am having the same error message also. I previously installed Visual Studio 2005 (not express). Could this have changed the sa password?|||

Hi, I've got the same problem - any ideas?

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40x4818

BUTTONS:

&Retry
Cancel

|||I have the same error during setup. I was upgrading a named instance of SSEE 2005 to SSEE w/ Advanced Services.

I used Windows Auth for the install; my windows account is a local admin on the server in question (Win2k Server) and my account has the sysadmin role in SQL Server.

I also tried it using SQL Server Auth with the SA account. That immediately showed the message:

"SQL Server Setup cannot upgrade the specified instance by using SQL Server credentials. You must use Windows Authentication credentials for the upgrade."

So, I find it strange that the setup fails with the message:

"SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information."
(The Error Number in the log summary is 29515)

It says the login failed for user 'sa' even though I used Windows Authentication.

Btw, I used the download posted here: http://msdn.microsoft.com/vstudio/express/sql/download/ Is that still a CTP?
|||More info from the error log:

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.

Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Wed Oct 26 16:37:41 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr

Error Code: 18456
MSI (s) (34!D4) [16:38:57:313]: Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Failure Type='Fatal' Error='18456'>
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='203'>
MSI (s) (34:C8) [16:38:57:360]: User policy value 'DisableRollback' is 0
MSI (s) (34:C8) [16:38:57:360]: Machine policy value 'DisableRollback' is 0
Action ended 16:38:57: InstallFinalize. Return value 3.
|||

Seems to be an issue that happens during upgrade.

In order to correctly upgrade from Express Edition to Express Edition with Advanced Services, follow the instructions in the SQL Express blog at: http://blogs.msdn.com/sqlexpress/archive/2006/04/20/UpgradeToAdvanced.aspx

If you've already tried to upgrade and received the error "Login failed for user 'sa'" then you will need to follow the instructions in the SQL Express blog at: http://blogs.msdn.com/sqlexpress/archive/2006/04/20/580312.aspx

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

|||Brilliant!
I ran into the same problem yesterday. Will try to use the blog posts to solve my problem. :)

Kaisa
|||The new version of SQLEXP_ADV worked just fine, I was using an earlier version saved on my CD's from Apr, but I just don't understand why these things just get so hard to fine. Great Job!!!! Keep up the hard work....

Problem Installing RS

I have a windows 2000 Ent. test server with IIS, SQL 2K Ent., ASP.NET
running. Today after I installed RS Std. version the ASP.NET stopped
working with a permission error. I chose not to install Report Designer and
asked because Visual Studio .NET isn't installed. Removing RS fixed will
fix the ASP.NET problem. I really lost here. On my XP box I tested with
SQL and RS worked fine. Don't know what's wrong here. Can you guys help?
Thx.it was a bug described in http://support.microsoft.com/kb/887787
"ME" <ME@.hotmail.com> wrote in message
news:%23zKPpsOVFHA.3184@.TK2MSFTNGP15.phx.gbl...
>I have a windows 2000 Ent. test server with IIS, SQL 2K Ent., ASP.NET
>running. Today after I installed RS Std. version the ASP.NET stopped
>working with a permission error. I chose not to install Report Designer
>and asked because Visual Studio .NET isn't installed. Removing RS fixed
>will fix the ASP.NET problem. I really lost here. On my XP box I tested
>with SQL and RS worked fine. Don't know what's wrong here. Can you guys
>help? Thx.
>

Problem inserting XML with DTD

Hi,
I am trying to insert a XML document into a SQL-Server 2005 column of type
XML:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE ctobject PUBLIC "-//my Ges.m.b.H.//DTD Procedural//EN"
"proced.dtd">
<ctobject>
<content>Some data with entity ref ü</content>
</ctobject>
The C#-Code for the operation is:
SqlConnection conn = new SqlConnection(connString);
conn.Open();
SqlCommand cmd = conn.CreateCommand();
cmd.CommandText = "Insert XmlData(XmlData) Values(@.Col1)";
SqlParameter p1 = cmd.Parameters.Add("@.Col1", SqlDbType.Xml);
XmlTextReader reader = new XmlTextReader(fn);
reader.XmlResolver = resolver;
p2.Value = new SqlXml(reader);
cmd.ExecuteNonQuery();
The operation produces an "InvalidOperationException" - "DTD is not allowed
in XML fragments" on instantiation of the "SqlXml" type.
Removing the DOCTYPE reference eliminates the problem but of course produces
another one: "XmlException" - "Reference to undeclared entity" (caused by
the "ü" entity reference).
What can I do.
Thanks in advance,
ErwinHello Erwin,
Since DTDs are not supported by SQL Server (but XML Schemas are :-) ) you
will have to replace the ü with something else (like <uuml/>, ü or
) and then replace it again on the client side (with ü) when you fetch
it back to the client.
You should however consider not using DTDs.
HTH
/Tobias|||Hello Tobias,
thank you for the response.
Unfortunately not using DTDs is currently not an option (large set of
technical documentation from customer, who is not prepared for switching to
schemas).
So if we decide to work with SQL-Server we will need some kind of
workaround:
usage of partial schemas for indexing (performance) purposes
storage of XML with resolved entities
...
Anyway, a very important requirement is to reproduce an identical copy of
the original document on store/retrieve operations. We will therefore need
some type of replace/restore operations (the way you mentioned in your
response). As an alternative we could try to store a copy of the original
XML to a simple "varchar" column. The first solution has the divantage of
producing extra computational overhead. It also ev. manipulates the original
document structure (ev. infuencing search operations). The second solution
produces redundant data with possible problems on data modification
activities.
Kind regards,
Erwin
"Tobias Thernstrm" <ttnospam@.rbam.nospam.se> schrieb im Newsbeitrag
news:ufcBW6pbGHA.4716@.TK2MSFTNGP03.phx.gbl...
> Hello Erwin,
> Since DTDs are not supported by SQL Server (but XML Schemas are :-) ) you
> will have to replace the ü with something else (like <uuml/>, ü
> or ) and then replace it again on the client side (with ü) when you
> fetch it back to the client.
> You should however consider not using DTDs.
> HTH
> /Tobias
>