Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts

Wednesday, March 28, 2012

More Info - HELP - Cannot connect to SQL Server 2005 Express

I've installed the SQL Server 2005 Express and also the MS SQL Server Management Studio 2005 Express
But when i load the latter and try to connect to my database I get the below error message.

TITLE: Connect to Server

Cannot connect to DEVCOMP\SQLEXPRESS.

ADDITIONAL INFORMATION:
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 Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Further Details:

Further to the above error me, I got the following when I clicked on "Surface Area Configuration for Services and Connections"

TITLE: Surface Area Configuration for Services and Connections - localhost
-
Computer localhost does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer has the required Windows Management Instrumentation components and then try again.
-
ADDITIONAL INFORMATION:
[C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll] InternalsVisibleTo declarations cannot have a version, culture, public key token, or processor architecture specified. (Microsoft.SqlServer.Smo)
-

|||Check to see if the SQL Server Express service is started.

Also, you may want to change the network settings to accept TCP/IP and remote connections. Check out this blog entry:

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Let me know if this doesn't fix your problem.

Thanks,
Rob|||

The remote connectivity is disabled by default. You can activate it using the SQL Server 2005 Surface Area Configuration SQLSAC.EXE.

If localhost is not known, then either your hosts. file is corrupt or blocked by a firewall (for any tests, deactivate the local firewall temporarily). You can use 127.0.0.1 instead of localhost.

The hosts file is located in your windows directory under

C:\windows\system32\drivers\etc\hosts.

Regards
Axel

|||

I have checked out the blog and performed all the steps. I have restarted the services and still no luck.

I am a newbie to webdev so started with the sample personal website. I followed the instructions to the letter but cant get past Ctrl-F5 to initialize without the error.

Where do I goto from here?

Paul

Monday, March 19, 2012

Monitoring SQL Server with MOM

We have recently installed MOM and wish to customise the SQL Management Pack.
What are the top alerts (10-20) we should be looking to alert on?This very much depends on your requirements. We are monitoring the following
events:
1. severe SQL Server errors (severity 17 or higher)
2. a database becomes inaccessible (excluding the cases in which the
database is being restored or offline)
3. the SQL instance becomes inaccessible
4. any port binding failure
5. any backup failure
6. any SQL instance restarts
7. clustered SQL instance not running on the preferred node
8. clustered SQL instance failover
9. cluster node not up (mostly the one that doesn't have any SQL instance
running)
10. # of connections exceeding a threshold (had some rough apps not cleaning
up after itself)
11. Free space below a certain threshold
Linchi
"Court" wrote:
> We have recently installed MOM and wish to customise the SQL Management Pack.
> What are the top alerts (10-20) we should be looking to alert on?|||Many thanks for that.
"Linchi Shea" wrote:
> This very much depends on your requirements. We are monitoring the following
> events:
> 1. severe SQL Server errors (severity 17 or higher)
> 2. a database becomes inaccessible (excluding the cases in which the
> database is being restored or offline)
> 3. the SQL instance becomes inaccessible
> 4. any port binding failure
> 5. any backup failure
> 6. any SQL instance restarts
> 7. clustered SQL instance not running on the preferred node
> 8. clustered SQL instance failover
> 9. cluster node not up (mostly the one that doesn't have any SQL instance
> running)
> 10. # of connections exceeding a threshold (had some rough apps not cleaning
> up after itself)
> 11. Free space below a certain threshold
> Linchi
> "Court" wrote:
> > We have recently installed MOM and wish to customise the SQL Management Pack.
> > What are the top alerts (10-20) we should be looking to alert on?|||Hi, is it possible for you to provide example event id's?
"Linchi Shea" wrote:
> This very much depends on your requirements. We are monitoring the following
> events:
> 1. severe SQL Server errors (severity 17 or higher)
> 2. a database becomes inaccessible (excluding the cases in which the
> database is being restored or offline)
> 3. the SQL instance becomes inaccessible
> 4. any port binding failure
> 5. any backup failure
> 6. any SQL instance restarts
> 7. clustered SQL instance not running on the preferred node
> 8. clustered SQL instance failover
> 9. cluster node not up (mostly the one that doesn't have any SQL instance
> running)
> 10. # of connections exceeding a threshold (had some rough apps not cleaning
> up after itself)
> 11. Free space below a certain threshold
> Linchi
> "Court" wrote:
> > We have recently installed MOM and wish to customise the SQL Management Pack.
> > What are the top alerts (10-20) we should be looking to alert on?

Monitoring SQL Server with MOM

We have recently installed MOM and wish to customise the SQL Management Pack
.
What are the top alerts (10-20) we should be looking to alert on?This very much depends on your requirements. We are monitoring the following
events:
1. severe SQL Server errors (severity 17 or higher)
2. a database becomes inaccessible (excluding the cases in which the
database is being restored or offline)
3. the SQL instance becomes inaccessible
4. any port binding failure
5. any backup failure
6. any SQL instance restarts
7. clustered SQL instance not running on the preferred node
8. clustered SQL instance failover
9. cluster node not up (mostly the one that doesn't have any SQL instance
running)
10. # of connections exceeding a threshold (had some rough apps not cleaning
up after itself)
11. Free space below a certain threshold
Linchi
"Court" wrote:

> We have recently installed MOM and wish to customise the SQL Management Pa
ck.
> What are the top alerts (10-20) we should be looking to alert on?|||Many thanks for that.
"Linchi Shea" wrote:
[vbcol=seagreen]
> This very much depends on your requirements. We are monitoring the followi
ng
> events:
> 1. severe SQL Server errors (severity 17 or higher)
> 2. a database becomes inaccessible (excluding the cases in which the
> database is being restored or offline)
> 3. the SQL instance becomes inaccessible
> 4. any port binding failure
> 5. any backup failure
> 6. any SQL instance restarts
> 7. clustered SQL instance not running on the preferred node
> 8. clustered SQL instance failover
> 9. cluster node not up (mostly the one that doesn't have any SQL instance
> running)
> 10. # of connections exceeding a threshold (had some rough apps not cleani
ng
> up after itself)
> 11. Free space below a certain threshold
> Linchi
> "Court" wrote:
>|||Hi, is it possible for you to provide example event id's?
"Linchi Shea" wrote:
[vbcol=seagreen]
> This very much depends on your requirements. We are monitoring the followi
ng
> events:
> 1. severe SQL Server errors (severity 17 or higher)
> 2. a database becomes inaccessible (excluding the cases in which the
> database is being restored or offline)
> 3. the SQL instance becomes inaccessible
> 4. any port binding failure
> 5. any backup failure
> 6. any SQL instance restarts
> 7. clustered SQL instance not running on the preferred node
> 8. clustered SQL instance failover
> 9. cluster node not up (mostly the one that doesn't have any SQL instance
> running)
> 10. # of connections exceeding a threshold (had some rough apps not cleani
ng
> up after itself)
> 11. Free space below a certain threshold
> Linchi
> "Court" wrote:
>

Wednesday, March 7, 2012

Monitor Server

I have few questions?
1. Can I implement log shipping into two systems which has
a SQL Server Enterprise Manager.
2. We can installed monitoring server on the standby or
have to need the separate server.
Thanks
David
Yes, you can setup Log Shipping between two SQL Servers.
Here is some info:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
I did not understand the second question.
Keith
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:089c01c50314$f10bd180$a601280a@.phx.gbl...
> I have few questions?
> 1. Can I implement log shipping into two systems which has
> a SQL Server Enterprise Manager.
> 2. We can installed monitoring server on the standby or
> have to need the separate server.
> Thanks
>
> David