Showing posts with label cant. Show all posts
Showing posts with label cant. Show all posts

Wednesday, March 21, 2012

Installed, but can't ping 1433

Any and all help is appreciated as project deadline is approaching...

Background:
- Two servers, 1 running WinXP with all updates and 1 running Win2K3 Standard with all updates.
- Both have SQL Express 2005 June CTP installed
- Both have Visual Studio 2005 Express installed.
- Installation finished w/o any errors.
- Services are running (browser and database)
- TCP/IP and named pipes are enabled

Issue:
Can't ping 127.0.0.1:1433.
OSQL times out without being able to establish a connection
Windows Firewall is OFF.

Seems to be a connectivity issue, but I'm a newbie and can't figure out why I can't talk to the database.

As I said, any and all help is appreciated. Thanks to all in advance.

PM

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

Installed, but can't ping 1433

Any and all help is appreciated as project deadline is approaching...

Background:
- Two servers, 1 running WinXP with all updates and 1 running Win2K3 Standard with all updates.
- Both have SQL Express 2005 June CTP installed
- Both have Visual Studio 2005 Express installed.
- Installation finished w/o any errors.
- Services are running (browser and database)
- TCP/IP and named pipes are enabled

Issue:
Can't ping 127.0.0.1:1433.
OSQL times out without being able to establish a connection
Windows Firewall is OFF.

Seems to be a connectivity issue, but I'm a newbie and can't figure out why I can't talk to the database.

As I said, any and all help is appreciated. Thanks to all in advance.

PM

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

sql

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previous
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Client
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'
Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:

> After installing SQL2005 (with a new instance), I couldn't access my previous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Client
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'
|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan
|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:

> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previou
s
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Clien
t
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:

> After installing SQL2005 (with a new instance), I couldn't access my previ
ous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Cli
ent
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:

> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>sql

Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previous
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Client
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:
> After installing SQL2005 (with a new instance), I couldn't access my previous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Client
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:
> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>

Monday, March 12, 2012

installation problem for SQL 2000 Development Edition

hi all, i dunno should i post it here or not but i cant other place to
post this problem ..

i am using windows XP professional service pack 1 .. when i try to
install MS SQL 2000 Developer Edition to my system, it can works fine
except when i try to set the user name and password then it promp out
this msg

error msg : setup cannot verify/grant logon as service right to the sql
server logon account : 1332(0X534)

can any 1 help me with this? if i choose windows authentichal password
then can run, i cannot set the password

--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996qintian (qintian.2cm19z@.no-mx.forums.yourdomain.com.au) writes:

Quote:

Originally Posted by

hi all, i dunno should i post it here or not but i cant other place to
post this problem ..
>
i am using windows XP professional service pack 1 .. when i try to
install MS SQL 2000 Developer Edition to my system, it can works fine
except when i try to set the user name and password then it promp out
this msg
>
error msg : setup cannot verify/grant logon as service right to the sql
server logon account : 1332(0X534)
>
can any 1 help me with this? if i choose windows authentichal password
then can run, i cannot set the password


The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server Service.
Right-click, Properties and on the second tab, you have log-on information.)

If you know that the account is alright, then I would just ignore the
message and move on. I believe, I've seen it when I've installed SQL Server
as well.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||thank you Erland Sommarskog,

so the time when i installing the MS SQL . i can juz simply choose a
log on mathod? then after that change it by your way? :confused:

--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996|||qintian (qintian.2cnvy0@.no-mx.forums.yourdomain.com.au) writes:

Quote:

Originally Posted by

thank you Erland Sommarskog,
>
so the time when i installing the MS SQL . i can juz simply choose a
log on mathod? then after that change it by your way? :confused:


Yes. If you're nervous that the installation will fail, you can choose
LocalSystem and then change to a normal Windows account after the
installation.

You can also change the choice of allowing SQL Server authentication after
the installation as well. Note that this concerns logging into SQL Server
itself.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||You can change this after the

Quote:

Originally Posted by

installation from the Services node in Computer Management.


I usually suggest that Enterprise manager be used to change the SQL Server
service account after installation because EM will grant additional advanced
user rights that don't get assigned with the Computer Management method.
The advanced rights are needed for functionality like changing security
context to the proxy account and using AWE. The permissions (documented in
the BOL) can be granted manually but it's more work.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns9821F12DE4F00Yazorman@.127.0.0.1...

Quote:

Originally Posted by

qintian (qintian.2cm19z@.no-mx.forums.yourdomain.com.au) writes:

Quote:

Originally Posted by

>hi all, i dunno should i post it here or not but i cant other place to
>post this problem ..
>>
>i am using windows XP professional service pack 1 .. when i try to
>install MS SQL 2000 Developer Edition to my system, it can works fine
>except when i try to set the user name and password then it promp out
>this msg
>>
>error msg : setup cannot verify/grant logon as service right to the sql
>server logon account : 1332(0X534)
>>
>can any 1 help me with this? if i choose windows authentichal password
>then can run, i cannot set the password


>
The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server
Service.
Right-click, Properties and on the second tab, you have log-on
information.)
>
If you know that the account is alright, then I would just ignore the
message and move on. I believe, I've seen it when I've installed SQL
Server
as well.
>
>
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||Dan Guzman (guzmanda@.nospam-online.sbcglobal.net) writes:

Quote:

Originally Posted by

I usually suggest that Enterprise manager be used to change the SQL
Server service account after installation because EM will grant
additional advanced user rights that don't get assigned with the
Computer Management method. The advanced rights are needed for
functionality like changing security context to the proxy account and
using AWE. The permissions (documented in the BOL) can be granted
manually but it's more work.


Interesting, I didn't know that. In fact, I was not even aware of that
you could change the service account through EM. I guess that shows how
much that I use Enterprise Manager. :-)

Thanks Dan for the information.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Dan Guzman Wrote:

Quote:

Originally Posted by

I usually suggest that Enterprise manager be used to change the SQL
Server
service account after installation because EM will grant additional
advanced
user rights that don't get assigned with the Computer Management
method.
The advanced rights are needed for functionality like changing
security
context to the proxy account and using AWE. The permissions
(documented in
the BOL) can be granted manually but it's more work.
>
--
Hope this helps.
>
Dan Guzman
SQL Server MVP
>
>


hi dan.. thanks for ur help but can u tell me more specified how to did
it with the EM ?? i finding whole day there but i cant find the security
part that u mentioning here..:( sorry need ur help again...

--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996|||qintian (qintian.2cpte2@.no-mx.forums.yourdomain.com.au) writes:

Quote:

Originally Posted by

hi dan.. thanks for ur help but can u tell me more specified how to did
it with the EM ?? i finding whole day there but i cant find the security
part that u mentioning here..:( sorry need ur help again...


Right-click the server node in EM, select Properties. Go the Security tab.
The lower third is for changing the service account.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Installation problem - can't find startup program

I installed SQL Server 2005.

In the add/remove programs are all the programs visible. But when I use "Start -> All programs -> Microsoft SQL Server 2005", there are only 5 configuration tools, no management studio.

What is going wrong?

Where can I find the executable that start up SQL Server 2005?

Hi,

you either installed SQL Server Express which does not come with a graphical administration surface (but you can either install the SQL Server Management Express Studio as an add-on or install the SQL Server Express Adavnced Edition from scratch which includes everything) or you deselected the Client tools option for any non-Express edition.

The tools for Express can be download from:

http://msdn.microsoft.com/vstudio/express/sql/download/

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Wednesday, March 7, 2012

installation of sp1. sql server integration services do not start

hi,

after installing sp1 for sql server 2005 the sql server integration services did not start. and i can`t start them manually. the installation succeeded without problems (both sql server and sp1)

the only problem was with installing sql server 2005. in the sql server configurations manager the following protocols were disabled:

- named pipes

- tcp/ip

- via

- shared memory was enabled

is this a problem. because in the "how to verify installation of sql server" is written, that tcp/ip has to be enabled. however i can manually enable it.

i can`t start the sql server integration services manually. so what can i do? i also tried reinstall sql server but i do get the same error.

hope somebody can help me!

Hi,

be sure to apply the post hotfixes, that fixes the issue around the SP1 and SSIS issue:

http://www.sqlserver2005.de/sqlserver2005/MyBlog/tabid/56/EntryID/7/Default.aspx

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de