Showing posts with label beginning. Show all posts
Showing posts with label beginning. Show all posts

Friday, March 30, 2012

Instance Name of SQL Server 2005 Standard

I'm new to SQL Server, and have just started to work through the MS Press ADO.Net 2.0 Step-by-Step book.

In the beginning of the book, at the point where the Add Connection box comes up, it says to type in the Server Name text box, (local)\SQLEXPRESS, as the book takes for granted you have SQL Express installed, and hence this is the instance name.

I have Visual Studio 2005 Professional, and SQL Server 2005 Standard installed. What would the instance of SQL Server be in this case?

Any hope would be greatly appreciated.

Unless you specifically gave it a name during setup then there is no instance name as its a default instance, hence you connect with (local)|||

when you have installed sql server standard (for that matter any edition) you will be asked whether u want to install Default Instance or Named Instance. Default instance will have the same name of your Physical Machine name and named instances will have Machinename\Nameof the instance. Just to see whether you have any instances running , just open Command window

c:\ sqlcmd -L

you will get all the instances running in the network. check howmany instance are there with your physical machine name

Madhu

|||

The default instance name for non-Express editions is MSSQLSERVER. But as already mentioned, you can use the machine name to connect if using a default instance.... or you can use MSSQLSERVER.

Thanks,

Sam Lester (MSFT)

|||

I just tried using the above as the instance of SQL Server, and while the Add Connection dialogue didn't say anything about the instance being invalid, it did give me the following error: "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: 25 - Connection string is not valid)"

I guess this is progress in a way...

Any suggestions? Do I need to re-install SQL Server? I do have a couple icons which mention SQL Server Configuration Manager, and SQL Server Management Studio, would anything there help?

Any suggestions would be appreciated...

|||Can you use SQl Server Config Manager and see if there are copies of sql server running and what their names are?|||

I have SQL Server Config Manager open now, however I'm clueless on what to do next, there really aren't many options.

On the left pane, under SQL Native Client Configuration, I see Client Protocols, and Aliases.

Under Client Protocols, the right pane shows: Shared Memory, Order 1, Enabled

TCP/IP, Order 2, Enabled

Named Pipes, Order 3, Enabled

VIA Disabled

Other than this, I really don't know what else to do...

Any help is appreciated...

|||

check whether the server is enabled for Remote Connections. Go to Surface Area Configuration tool and check it. Also check firewall is enabled on this machine. if yes excempt TCP port 1433 and UDP 1434

Madhu

|||select the services node and post back what you find|||

I have no idea how to do any of this, or where it's located...

Sorry, I've never used SQL before...

|||

From where?

Sorry, I've never used SQL before...

|||

refer this link http://support.microsoft.com/kb/914277

Madhu

|||

Euan Garden wrote:

select the services node and post back what you find

what Euan mentioned is -- GO to control pannel -- Administraive tools -- Services and see what all are the services running with the name SQLServer * and post back the names of the services running on the machine

Madhu

|||

There are many services listed on two tabs, standard and extended.

However, there is nothing listed that begins with SQL.

I have no idea what to do from here, sorry..

|||

if there is no services running with name like SQL Server (MSSQLSERVER) or SQLServer (SQLExpress) etc etc.. then you have only installed client tool. In this physical machine there is no Database Engine installed. Either re-install the sql server and choose what all are the services you need or connect to any other machine which already have sql server

Madhu

sql

Friday, February 24, 2012

Installing SQL Errors - Anyone please read my log file

Microsoft SQL Server 2005 Setup beginning at Sat Jan 14 20:31:52 2006
Process ID : 896
c:\ef878dcc6c3c3c0766424d939e4b7c78\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/0/14 20:31:51
Complete: LoadResourcesAction at: 2006/0/14 20:31:51, returned true
Running: ParseBootstrapOptionsAction at: 2006/0/14 20:31:51
Loaded DLL:c:\ef878dcc6c3c3c0766424d939e4b7c78\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/0/14 20:31:52, returned true
Running: ValidateWinNTAction at: 2006/0/14 20:31:52
Complete: ValidateWinNTAction at: 2006/0/14 20:31:52, returned true
Running: ValidateMinOSAction at: 2006/0/14 20:31:52
Complete: ValidateMinOSAction at: 2006/0/14 20:31:52, returned true
Running: PerformSCCAction at: 2006/0/14 20:31:52
Complete: PerformSCCAction at: 2006/0/14 20:31:52, returned true
Running: ActivateLoggingAction at: 2006/0/14 20:31:52
Complete: ActivateLoggingAction at: 2006/0/14 20:31:52, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__896" returned false.
Running: PerformSCCAction2 at: 2006/0/14 20:31:52
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032

I have scraped this maching clean and still get the residue beta version exception. Got any clues to find this stuff that exist on my machine- XP home addtion

In the note log it says Watson failed.

Try the following.

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.
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.

Or you can send me email so I can send a script for you to clean beta components.