Re: Sql Server 2008 Developer Edition
- From: DaveS <DaveS@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 30 Sep 2008 14:27:02 -0700
I am doing it through SSMS 2008. I have it set to open to Object Explorer
and a query. The query window's tab show SQLQuery1.sql. Below it is "Mining
Model", a drop down box with Not Connected in it and below that a Metadata
and Functions tabs. When I select this query window I can go up to the menu
bar and turn off the Metadata part. Now that I just have Sql2008 installed
(with Integration Svcs) when I try and do a connection within the query
window it the connection object says it is connected even though at the
bottom it shows disconnected.
So I do a change connection and the connection popup shows Analysis Services
greyed out and the original database. I change it to master by going to the
Connection Properties tab and change the instance to the correct one (SS8).
The error message box comes back with a title of "Connect to Analysis
Services" and then below that title it shows cannot connect to 800IS187\SS8
with additional info.
I've been thru the logs and none of these are being logged to the error log.
Can you have Sql 2005 dev ed. and 2008 dev ed. both installed? Seems like
back several versions that there was a special order to use to install them
(I go back to version 4.5).
I also have Vis Studio 2008 Database edition installed with sp1. The
original install of Sql 2008 went without a problem. Below is the log for
the 3rd (most recent) install:
Server Microsoft SQL Server 2008 (RTM) - 10.0.1763.0 (Intel X86)
Sep 18 2008 21:13:29
Copyright (c) 1988-2008 Microsoft Corporation
Developer Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)
2008-09-30 13:29:38.25 Server Error: 17054, Severity: 16, State: 1.
2008-09-30 13:29:38.25 Server The current event was not reported to the
Windows Events log. Operating system error = 1502(The event log file is
full.). You may need to clear the Windows Events log if it is full.
2008-09-30 13:29:38.27 Server (c) 2005 Microsoft Corporation.
2008-09-30 13:29:38.27 Server All rights reserved.
2008-09-30 13:29:38.27 Server Server process ID is 5640.
2008-09-30 13:29:38.27 Server Authentication mode is MIXED.
2008-09-30 13:29:38.27 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL10.SS8\MSSQL\Log\ERRORLOG'.
2008-09-30 13:29:38.30 Server This instance of SQL Server last reported
using a process ID of 4276 at 9/30/2008 1:19:42 PM (local) 9/30/2008 6:19:42
PM (UTC). This is an informational message only; no user action is required.
2008-09-30 13:29:38.30 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.SS8\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.SS8\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.SS8\MSSQL\DATA\mastlog.ldf
2008-09-30 13:29:38.42 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2008-09-30 13:29:38.42 Server Detected 2 CPUs. This is an informational
message; no user action is required.
2008-09-30 13:29:40.86 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2008-09-30 13:29:43.33 Server Node configuration: node 0: CPU mask:
0x00000003 Active CPU mask: 0x00000003. This message provides a description
of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2008-09-30 13:29:44.41 spid7s Starting up database 'master'.
2008-09-30 13:29:45.30 spid7s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2008-09-30 13:29:46.45 spid7s Resource governor reconfiguration
succeeded.
2008-09-30 13:29:46.50 spid7s SQL Server Audit is starting the audits.
This is an informational message. No user action is required.
2008-09-30 13:29:46.59 spid7s SQL Server Audit has started the audits.
This is an informational message. No user action is required.
2008-09-30 13:29:46.69 spid7s FILESTREAM: effective level = 0,
configured level = 0, file system access share name = 'SS8'.
2008-09-30 13:29:47.95 spid7s SQL Trace ID 1 was started by login "sa".
2008-09-30 13:29:48.08 spid7s Starting up database 'mssqlsystemresource'.
2008-09-30 13:29:48.14 spid7s The resource database build version is
10.00.1763. This is an informational message only. No user action is required.
2008-09-30 13:29:49.38 spid10s Starting up database 'model'.
2008-09-30 13:29:49.42 spid7s Server name is '800IS187\SS8'. This is an
informational message only. No user action is required.
2008-09-30 13:29:50.08 spid10s Clearing tempdb database.
2008-09-30 13:29:52.34 Server A self-generated certificate was
successfully loaded for encryption.
2008-09-30 13:29:52.56 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\SS8 ].
2008-09-30 13:29:52.56 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\MSSQL$SS8\sql\query ].
2008-09-30 13:29:52.94 spid10s Starting up database 'tempdb'.
2008-09-30 13:29:53.41 Server Server is listening on [ 127.0.0.1 <ipv4>
1926].
2008-09-30 13:29:53.41 Server Dedicated admin connection support was
established for listening locally on port 1926.
2008-09-30 13:29:53.64 Server The SQL Server Network Interface library
successfully registered the Service Principal Name (SPN) [
MSSQLSvc/800IS187.US.chs.net:SS8 ] for the SQL Server service.
2008-09-30 13:29:53.64 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2008-09-30 13:29:53.75 spid14s The Service Broker protocol transport is
disabled or not configured.
2008-09-30 13:29:53.80 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2008-09-30 13:29:54.19 spid14s Service Broker manager has started.
2008-09-30 13:29:55.14 spid13s A new instance of the full-text filter
daemon host process has been successfully started.
2008-09-30 13:29:55.45 spid7s Starting up database 'msdb'.
2008-09-30 13:29:56.28 spid7s Recovery is complete. This is an
informational message only. No user action is required.
2008-09-30 13:30:03.11 spid51 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2008-09-30 13:30:03.11 spid51 FILESTREAM: effective level = 0,
configured level = 0, file system access share name = 'SS8'.
2008-09-30 13:30:03.27 spid51 Configuration option 'Agent XPs' changed
from 0 to 1. Run the RECONFIGURE statement to install.
2008-09-30 13:30:03.27 spid51 FILESTREAM: effective level = 0,
configured level = 0, file system access share name = 'SS8'.
2008-09-30 13:30:03.52 spid51 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2008-09-30 13:30:03.52 spid51 FILESTREAM: effective level = 0,
configured level = 0, file system access share name = 'SS8'.
2008-09-30 13:30:14.08 spid51 Attempting to load library 'xpsqlbot.dll'
into memory. This is an informational message only. No user action is
required.
2008-09-30 13:30:14.22 spid51 Using 'xpsqlbot.dll' version
'2007.100.1600' to execute extended stored procedure 'xp_qv'. This is an
informational message only; no user action is required.
2008-09-30 13:30:15.20 spid51 Attempting to load library 'xpstar.dll'
into memory. This is an informational message only. No user action is
required.
2008-09-30 13:30:15.81 spid51 Using 'xpstar.dll' version
'2007.100.1600' to execute extended stored procedure 'xp_instance_regread'.
This is an informational message only; no user action is required.
2008-09-30 13:30:16.94 spid51 Attempting to load library 'xplog70.dll'
into memory. This is an informational message only. No user action is
required.
2008-09-30 13:30:17.23 spid51 Using 'xplog70.dll' version
'2007.100.1600' to execute extended stored procedure 'xp_msver'. This is an
informational message only; no user action is required.
Any suggestions on what I should try next? I downloaded this version using
our MSDN subscription about 3 weeks ago.
Thanks,
Dave
"Aaron Bertrand [SQL Server MVP]" wrote:
.The 3rd installation isstill trying to do MSAS when I try to run a query against the Master db
Can you explain in detail the steps you take before you "try to run a
query"? Are you doing this in Management Studio 2005, Management Studio
2008, Business Intelligence Development Studio (BIDS) 2005, BIDS 2008,
Visual Studio, or something else? Is it a new query window? What did you
do before the new query window appeared?
I agree that the uninstaller tool does not clean up old instances as well as
it should. I complained about this here:
http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=32905
4
(Please try to ignore the spam by one Brian Shepherd.)
The "fix" they talk about is not actually the tool that they promised, but
rather a KB article that explained all the hoops you need to go through. As
far as I can tell, the KB article hasn't been delivered yet, either. I just
re-activated the issue.
But anyway, it shouldn't be screwing you up this badly... I think there is
some mix-up in exactly what you should be doing to get a database engine
query window open and connected correctly before you "try to run a query"...
- Follow-Ups:
- Re: Sql Server 2008 Developer Edition
- From: Aaron Bertrand [SQL Server MVP]
- Re: Sql Server 2008 Developer Edition
- Prev by Date: Varying component versions in BIDS
- Next by Date: Re: Sql Server 2008 Developer Edition
- Previous by thread: Varying component versions in BIDS
- Next by thread: Re: Sql Server 2008 Developer Edition
- Index(es):
Relevant Pages
|
Loading
