SQL Server - SQL Server Setup Problem (2000 / 2005)

Asked By Joseph Geretz
02-Nov-08 10:48 PM
I'm having a problem setting up a developer's workstation with SQL Server
(Developer Edition). Here's the behavior I'm seeing:

A couple of days ago we set up a developers workstation. This is a complex
environment consisting of Windows XP Pro SP 2, a number of Server elements
(SQL Server 2000 / 2005,  IIS) a number of development tools (Visual Studio
6, Visual Studio 2005) and a number of Office products (2003 and 2007). To
my chagrin, when we installed our production database into the SQL Server
environment via a Restore, we received numerous errors in trying to access
the database via our application. Finally, we tracked this down to database
corruption using DBCC CHECKDB. Strange. This database (a demo database) is
restored to many, many environments with no problem whatesoever. At first I
was incined to chalk this up to a bad environmental setup.

OK, we tore down the entire environment, reimaged back to the base OS and
begain first by installing SQL Server 2000 and SQL Server 2005. Before
proceeding to install any additional software we restored the database into
both SQL Server 2000 and 2005 environments. We ran DBCC CHECKDB and the
databases checked out flawlessly with no errors. We then proceeded to
install all of the adidtional necessary devleopment and productivity
software.

Well, guess what happened after getting all additional software installed.
You got it - DBCC CHECKDB returns the same errors which we were getting two
days ago! I'm at a loss to explain this. The database backup file is the
same physical file which installs flawlessly into dozens of SQL Server 2000
/ 2005 environment. To all appearances the SQL Server environment on this
new machine is identical to the SQL Server environment which is set up on my
personal workstation and which restores this backup file flawlessly with no
problem. I don't even know how to go about diagnosing this problem.

I am including the error lines form the DBCC CHECKDB following my signature.
If you've ever seen this type of problem, or if you have suggestions for how
to go about diagnosing this problem, I'll be grateful for any advice which
you can provide.

Thanks!

Joseph Geretz

--------------------
DBCC CHECKDB:

Server: Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID 0: Page (1:5929) could not be processed. See other
errors for details.
DBCC results for 'FreedomDEMO'.
CHECKDB found 1 allocation errors and 0 consistency errors not associated
with any single object.

...

DBCC results for 'INTEGRATIONMSGMAP'.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5928) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:5929) is pointed to by the next pointer of IAM page (0:0) object
ID 1993058136 index ID 0 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 1993058136, index ID 0 due to invalid
allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5929) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1993058136, index ID 0, page (1:5929). Test (IS_ON
(BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:5806), slot 1, text ID 4718919680 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:5806), slot 2, text ID 4719312896 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:5920), slot 1, text ID 17104896 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:10522), slot 1, text ID 5243011072 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:10542), slot 1, text ID 4849729536 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:10542), slot 2, text ID 4849795072 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:10542), slot 3, text ID 4851171328 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1993058136. The text, ntext, or image node at page
(1:10542), slot 4, text ID 4851367936 is not referenced.
There are 0 rows in 0 pages for object 'INTEGRATIONMSGMAP'.

...

DBCC results for 'APPLICATIONINFO'.
There are 0 rows in 0 pages for object 'APPLICATIONINFO'.
CHECKDB found 3 allocation errors and 10 consistency errors in table
'APPLICATIONINFO' (object ID 1993058136).

...

CHECKDB found 4 allocation errors and 10 consistency errors in database
'FreedomDEMO'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (FreedomDEMO ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
SQL Server 2000
(1)
SQL Server 2005
(1)
SQL Server 2008
(1)
SQL Server
(1)
Windows XP
(1)
Virtual PC
(1)
Visual Studio 2005
(1)
Visual Studio
(1)
  Sylvain Lafontaine replied...
03-Nov-08 12:03 AM
You should install these stuff in the order that they have been released by
Microsoft; including the service packs wherever possible.  Here's a
possibility:

1- VS6
2- SQL-Server 2000
3- Office 2003
4- SQL-Server 2005
5- VS 2005
6- Office 2007
7- SP3 for Windows XP
8 - VS 2008 + SP1
9 - SQL-Server 2008

For the latest SP for each of these softwares, I'm not sure.  In case of
doubt, reinstall one of the component above the others.  I would say it's
very important to install VS6 because it's now a very old piece of software.

For IIS, I don't know.

You must also make sure for the restoration process that you have the same
SP for the local version of SQL-Server than from the one on which the backup
has been made (or newer, never older).

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
  Uri Dimant replied...
03-Nov-08 12:10 AM
Joseph
Was you able to identify what exact software caused the error? Is it office
2007 product?
Do you have SQL Server Service Pack 2?
  Joseph Geretz replied...
03-Nov-08 01:59 AM
Uri, Sylvain, thanks for your replies.

How can I tell what version of SQL Server service packs have been installed?
Is this available from Enterprise Manager? SQL Server Properties dialog
shows 8.00.194 (RTM) but other than that, I don't see the service pack level
displayed. Where can I find this?

Thanks!

Joseph Geretz
  Uri Dimant replied...
03-Nov-08 03:22 AM
Hi
SELECT @@VERSION
http://dimantdatabasesolutions.blogspot.com/2007/04/whats-version-of-sql-server.html
  Aaron Bertrand [SQL Server MVP] replied...
03-Nov-08 04:08 PM
That is probably Help|About in Enterprise Manager, which tells you the
version of the tools, not the server you are connecting to...

You should apply an update (e.g. SP4) to your client components.  Since I
haven't had to use SQL Server 2000 in some time, I forget where all of the
updates came in, but there have certainly been some updates to Enterprise
Manager, Query Analyzer and other client tools since SQL Server 2000 was
first released.

To tell the version of the server, highlight its name in the registered
servers list in Enterprise Manager, go to Tools | Query Analyzer, type
  Joseph Geretz replied...
03-Nov-08 10:55 PM
OK, thanks guys. Here's what I found:

SELECT @@VERSION returns the following on my workstation, which is OK:

Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)

Here's what it returns on the workstation which is producing the errors:

Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)

It's the same version and server pack on both workstations.

OK, so in desperation I download and install SP4. Here's what SELECT
@@VERSION returns with SP4 installed:

Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)

????!!!!!

Why does it still show SP2 with SP4 installed??!! (Mind you, I'm running
this while logged in to the workstation using the SQL Query Analyzer which
is actually installed on the server. I'm not doing this remotely.)

I'm baffled.

Joseph Geretz
  Jeffrey Williams replied...
03-Nov-08 11:15 PM
Running SELECT @@VERSION does not show you the version of the client
tools.  It shows you the version of SQL Server that Query Analyser
window is connected to.

And finally, when you run @@VERSION you get both the version of SQL and
the OS.  What you are seeing as Service Pack 2 is the version of the OS.

*** on Windows NT 5.1 (Build 2600: Service Pack 2) ***

tells us the OS Build and Service Pack FOR THE OS.
  Joseph Geretz replied...
03-Nov-08 11:48 PM
Hi Jeffrey,





Thanks for explaining that.





Yes, this is exactly what I'd like to see. How can I walk up to a SQL Server
box and get information regarding what SP level the SQL Server is patched up
to?



By the way, I have managed to solve the problem. When things just don't make
sense, it's time to try something different.



On my own workstation, I personally restored the database form the same
backup file which was causing problems on the other workstation. I then
created a new database backup on my workstation. This new backup restores
perfectly into the target SQL Server 2000 environment. In retrospect, it
seems to me that the entire problem was due to some sort of corruption in
the original database backup file. How this file restored into my
environment with no problem is something which will probably remain a
mystery.



Thanks all for your help!



Joseph Geretz
  paraskarsatis replied...
28-Nov-08 11:40 PM
OS.
w
ke
8:38
s:
8:38
8:38
)
e
ince
d
e
w
OS.

hi,i have problem installing sql server 2005 development edition on xp
sp2 os.i am installing sql server in mixed mode.after installation i
am able 2 login in windows authentication mode,but when i am trying to
login in sql server authentication mode it is giving some error:
18456,severity:14.please help me out
  ekre replied...
28-Nov-08 04:06 AM
After installing SP2, sometimes Authentication Mode changes to Windows
Authentication only. I don't exactly know what causes this change yet,
however I suggest you to check Authentication Mode from Server Properties
again.

If this is not the issue, then check out SQL Error Logs for more information
and ensure that the Login you try to log in is enabled and your password is
correct.

--
Ekrem Önsoy




hi,i have problem installing sql server 2005 development edition on xp
sp2 os.i am installing sql server in mixed mode.after installation i
am able 2 login in windows authentication mode,but when i am trying to
login in sql server authentication mode it is giving some error:
18456,severity:14.please help me out
  thejami replied...
08-Feb-09 12:53 PM
Sylvain,
While this makes sense... in my experience it has not been true.  For
example, anything that may disable features from an earlier version will
cause issues.  In general, again, in may experience, it has been more
successful when issues arise, to install the latest first, then install the
previous and actually work the other way.
IMHO...
--
Regards,
Jamie
  Tibor Karaszi replied...
09-Feb-09 05:43 AM
Jamie,


But perhaps that disabling is for a good reason.? I agree with John
here. For instance, if you install SQL Server 2000 after 2005, you
will mess about with some aspects of your 2005 installation. And the
reason is that SQL Server 2005 didn't exist when they wrote the SQL
Server 2000 installation program.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
Create New Account
help
Cannot restart SQL Server service SQL Server I recently installed SQL Server 2008 Express Edition with Advanced Tools. This is the version information from SQL Server Management Studio Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709- 1414
Access 2007-> SQL Server2005 "connection was forcibly closed", GNE 1 SQL Server SQL, Server2005, "connection, was, forcibly, closed", GNE, 1" / > Hi, with an Access 2007 application, I have a very big problem connecting an SQL Server 2005. The scenario: - nearly 200 clients with Windows XP Professional (in an Active Directory Domain) - clients uses WAN, LAN and WLAN, different locations
SQL Express: Failed Reinstall SQL Server Dear Setup Experts: I am trying to reinstall SQL Express after playing with it some. I uninstalled it, and now, it refuses to reinstall in the face. Any ideas what this log file means and how I can get SQL Express installed? I really do not want to have to reinstall my whole system. * ** ** Start of Log File Overall summary: Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup. Exit code (Decimal): -2068643839 Exit facility code: 1203
Don't understand what version of SQL to install SQL Server I feel silly asking, but I'm a beginner. I have access to all MS SQL Servers, the express, workgroup, standard, developer, and the enterprise version, both 2005 and 2008. My question is, which one should I install for creating client websites. There are so many different version out there. For example, if I have one client that uses sql 2005 standard, one with sql 2008 enterprise, am I suppose to install them all. Goodness??? Can
Sql Remote Connection issue SQL Server I am trying to setup Sql Server 2000 to handle remote connections from the web. I have setup the firewall to allow port 1433 to be redirected back to the internal Sql Server which I know is working. To verify the connection I am using telnet to verify