CAN'T FULLY UNINSTALL SQL SERVER 2005 STANDARD

We have a Windows Server 2003 SP1 machine with two hard drives. I
installed MS SQL Server 2005 without paying attantion to where it
installed to. The c: drive is very small while d: is large. SQL
installed on c:. Apparentely, log files were growing and filled up all
the space on c:. I couldn't access SQL Server and decided uninstall it.
I went ahead and uninstall all components via add/remove programs.
After that I noticed all sql folders on c: are present, all services
are running and I was able to open Management Studio. At the same time
no SQL products are listed in add/remove. I need to fully uninstall it.
I tried command prompt pointing to the setup.exe file (where I copied
disks since it is a remote server) and failed.
Please, help!!!
StanYou did a reboot, right?
"suslikovich" <suslikovich@.yahoo.com> wrote in message
news:1146518232.810806.181140@.y43g2000cwc.googlegroups.com...
> We have a Windows Server 2003 SP1 machine with two hard drives. I
> installed MS SQL Server 2005 without paying attantion to where it
> installed to. The c: drive is very small while d: is large. SQL
> installed on c:. Apparentely, log files were growing and filled up all
> the space on c:. I couldn't access SQL Server and decided uninstall it.
> I went ahead and uninstall all components via add/remove programs.
> After that I noticed all sql folders on c: are present, all services
> are running and I was able to open Management Studio. At the same time
> no SQL products are listed in add/remove. I need to fully uninstall it.
> I tried command prompt pointing to the setup.exe file (where I copied
> disks since it is a remote server) and failed.
> Please, help!!!
> Stan
>|||Yes, I did a reboot after I uninstalled all sql products.
Stan

can't find maintenance plan wizard in MSS2005

Hello,
I use sql server 2005 standard edition, sp1 installed on win2003server.
I can't find the maintenance plan wizard in the object explorer in the
management-studio.
In documentation I found out, that the user connection must be done via
windows authentication and you have to
be a role-member of sysadmin (what does this mean exactly?).
Furthermore databases must have a compatibility of 80 (MSS2000) or
higher.
I met all conditions, but I still can't use the wizard.
Any ideas how to make the wizard 'visible' or is there a command line
statement to call it?
Thanks for any help!In SSMS open Management and right click on Maintenance Plans. The
second options is the manitenance plan wizard.
Markus|||MarkusB wrote:
> In SSMS open Management and right click on Maintenance Plans. The
> second options is the manitenance plan wizard.
> Markus
Already the item 'Maintenance Plans' under Management is missing !!!
Only under the subitem Legacy there is a item 'Database Maintenance
Plans'.
But rightclicking there doesn't show the wizard-item.
anymore ideas?|||keltchen wrote on 7 Aug 2006 03:58:42 -0700:

> MarkusB wrote:
> Already the item 'Maintenance Plans' under Management is missing !!!
> Only under the subitem Legacy there is a item 'Database Maintenance
> Plans'.
> But rightclicking there doesn't show the wizard-item.
> anymore ideas?
You did what I did - didn't install SQL Server Integration Services. The
Maintenance Plan Wizard (and the interface to plans from SMSS) is part of
SSIS. Install SSIS from the SQL Server CD and you should get it working.
Dan

can't find maintenance plan wizard in MSS2005

Hello,
I use sql server 2005 standard edition, sp1 installed on win2003server.
I can't find the maintenance plan wizard in the object explorer in the
management-studio.
In documentation I found out, that the user connection must be done via
windows authentication and you have to
be a role-member of sysadmin (what does this mean exactly?).
Furthermore databases must have a compatibility of 80 (MSS2000) or
higher.
I met all conditions, but I still can't use the wizard.
Any ideas how to make the wizard 'visible' or is there a command line
statement to call it?
Thanks for any help!In SSMS open Management and right click on Maintenance Plans. The
second options is the manitenance plan wizard.
Markus|||MarkusB wrote:
> In SSMS open Management and right click on Maintenance Plans. The
> second options is the manitenance plan wizard.
> Markus
Already the item 'Maintenance Plans' under Management is missing !!!
Only under the subitem Legacy there is a item 'Database Maintenance
Plans'.
But rightclicking there doesn't show the wizard-item.
anymore ideas?|||keltchen wrote on 7 Aug 2006 03:58:42 -0700:
> MarkusB wrote:
>> In SSMS open Management and right click on Maintenance Plans. The
>> second options is the manitenance plan wizard.
>> Markus
> Already the item 'Maintenance Plans' under Management is missing !!!
> Only under the subitem Legacy there is a item 'Database Maintenance
> Plans'.
> But rightclicking there doesn't show the wizard-item.
> anymore ideas?
You did what I did - didn't install SQL Server Integration Services. The
Maintenance Plan Wizard (and the interface to plans from SMSS) is part of
SSIS. Install SSIS from the SQL Server CD and you should get it working.
Dan

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:
> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post :) Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
> > hi everyone,
> >
> > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > SP2.
> >
> > The database itself is checked with "2000 sql compatible". I also have TCP,
> > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > and SQL authentication with my sa account.
> >
> > I just created a maintenance plan in the Studio console so that the backup
> > and reindex can run on the server db. However, the job failed last nite. I
> > decide delete the plan and set up another one. I connected to the server by
> > using the Studio console on itself and tried to remove the plan, but it
> > failed. I clicked on the error (a link displayed in the Studio) said the
> > following:
> >
> > #############
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > Additional information:
> > An error has occurred while establishing a connection to the server. When
> > connecting to the SQL server 2005, this failure may be caused by the fact
> > that under the default settings SQL server does not allow remote connections.
> > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > Server)(Microsoft SQL server, Error:53)
> > ##############
> >
> > I have made sure the remote connection (right click on the server object in
> > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > is enabled (\\.\pipe\sql\query).
> >
> > May you provide idea so that I can remove the plan successfully?
> >
> > Thank you!
> >
> > Bobson|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since Iâ'm running on a cluster, after the maintenance plan was created. I
know thatâ's related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
> Dennis,
> Great someone read my post :) Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
> > Were you able to fix your problem? I have the same issue but didn't found
> > anything helpful yet.
> >
> > Thanks
> >
> > Denis Desjardins
> >
> > "Bobson" wrote:
> >
> > > hi everyone,
> > >
> > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > SP2.
> > >
> > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > and SQL authentication with my sa account.
> > >
> > > I just created a maintenance plan in the Studio console so that the backup
> > > and reindex can run on the server db. However, the job failed last nite. I
> > > decide delete the plan and set up another one. I connected to the server by
> > > using the Studio console on itself and tried to remove the plan, but it
> > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > following:
> > >
> > > #############
> > > Exception has been thrown by the target of an invocation. (mscorlib)
> > >
> > > Additional information:
> > > An error has occurred while establishing a connection to the server. When
> > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > that under the default settings SQL server does not allow remote connections.
> > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > Server)(Microsoft SQL server, Error:53)
> > > ##############
> > >
> > > I have made sure the remote connection (right click on the server object in
> > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > is enabled (\\.\pipe\sql\query).
> > >
> > > May you provide idea so that I can remove the plan successfully?
> > >
> > > Thank you!
> > >
> > > Bobson|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since Iâ'm running on a cluster, after the maintenance plan was created. I
> know thatâ's related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
> > Dennis,
> >
> > Great someone read my post :) Before telling my point of view... I would
> > like to ask if you do the following :
> >
> > 1.) Put the sql in the domain
> > 2.) rename the server couple times as the task already created
> > 3.) use different admin account to log on and config both sql and OS (I am
> > still thinking permission related)
> >
> > I have no one to respond to me as I could not find any solution on the Net
> > (the closest one is to run some scripts and clean up registry). The problem
> > still remains. But I did a test by setting up a clean new server with the
> > SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> > mentioned above...
> >
> > I was about to submit an issue to MS... but the SQL admin finally said we
> > could ignore the issue...so I just seize my action.
> >
> > May I get your person email so we can talk more about it? Mine is
> > ultrabobson@.hotmail.com
> >
> > Thank you, and stay in touch.
> >
> > Bobson
> >
> >
> >
> > "Denis Desjardins" wrote:
> >
> > > Were you able to fix your problem? I have the same issue but didn't found
> > > anything helpful yet.
> > >
> > > Thanks
> > >
> > > Denis Desjardins
> > >
> > > "Bobson" wrote:
> > >
> > > > hi everyone,
> > > >
> > > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > > SP2.
> > > >
> > > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > > and SQL authentication with my sa account.
> > > >
> > > > I just created a maintenance plan in the Studio console so that the backup
> > > > and reindex can run on the server db. However, the job failed last nite. I
> > > > decide delete the plan and set up another one. I connected to the server by
> > > > using the Studio console on itself and tried to remove the plan, but it
> > > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > > following:
> > > >
> > > > #############
> > > > Exception has been thrown by the target of an invocation. (mscorlib)
> > > >
> > > > Additional information:
> > > > An error has occurred while establishing a connection to the server. When
> > > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > > that under the default settings SQL server does not allow remote connections.
> > > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > > Server)(Microsoft SQL server, Error:53)
> > > > ##############
> > > >
> > > > I have made sure the remote connection (right click on the server object in
> > > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > > is enabled (\\.\pipe\sql\query).
> > > >
> > > > May you provide idea so that I can remove the plan successfully?
> > > >
> > > > Thank you!
> > > >
> > > > Bobson

can''t create reports via VS 2005 Standard

From what I read about the versions, VS 2005 Standard allows for SSRS development.

If I create a new project, I don't see the option to create anything from the BI section to create a report project.

I have SQL Server Express on my machine, and am able to run the SSRS configuartion management tool.

Do I have to run an .exe file or something?

Thanks!

When you installed SQL, did you expand all of the components and specify that you WANT them to be installed? For some reason they all default to do NOT intall.

I believe there is a component in client components (business intelligence studio) or something like that which actually installs the SQL server report project to Visual Studio.

Yes, Visual Studio comes with a menu in the create project wizard for Business Intelligence Projects. However, there are most likely no project types in that section for you, because the proper components were not installed when SQL was installed.

|||You have to install the SQL Server 2005 workstation tools including the Business Intelligence Studio AFTER VS 2005 is installed, and several new modules will show in the VS2005 startup splash, and new project types will be available.

If this still does not appear properly, you may need to rebuild your project templates. I took me a couple re-installs to get it right.
|||

did a re-install of the tool set which includes the BI templates and that worked.

Thanks!

can''t create reports via VS 2005 Standard

From what I read about the versions, VS 2005 Standard allows for SSRS development.

If I create a new project, I don't see the option to create anything from the BI section to create a report project.

I have SQL Server Express on my machine, and am able to run the SSRS configuartion management tool.

Do I have to run an .exe file or something?

Thanks!

When you installed SQL, did you expand all of the components and specify that you WANT them to be installed? For some reason they all default to do NOT intall.

I believe there is a component in client components (business intelligence studio) or something like that which actually installs the SQL server report project to Visual Studio.

Yes, Visual Studio comes with a menu in the create project wizard for Business Intelligence Projects. However, there are most likely no project types in that section for you, because the proper components were not installed when SQL was installed.

|||You have to install the SQL Server 2005 workstation tools including the Business Intelligence Studio AFTER VS 2005 is installed, and several new modules will show in the VS2005 startup splash, and new project types will be available.

If this still does not appear properly, you may need to rebuild your project templates. I took me a couple re-installs to get it right.
|||

did a re-install of the tool set which includes the BI templates and that worked.

Thanks!

can''t create reports via VS 2005 Standard

From what I read about the versions, VS 2005 Standard allows for SSRS development.

If I create a new project, I don't see the option to create anything from the BI section to create a report project.

I have SQL Server Express on my machine, and am able to run the SSRS configuartion management tool.

Do I have to run an .exe file or something?

Thanks!

When you installed SQL, did you expand all of the components and specify that you WANT them to be installed? For some reason they all default to do NOT intall.

I believe there is a component in client components (business intelligence studio) or something like that which actually installs the SQL server report project to Visual Studio.

Yes, Visual Studio comes with a menu in the create project wizard for Business Intelligence Projects. However, there are most likely no project types in that section for you, because the proper components were not installed when SQL was installed.

|||You have to install the SQL Server 2005 workstation tools including the Business Intelligence Studio AFTER VS 2005 is installed, and several new modules will show in the VS2005 startup splash, and new project types will be available.

If this still does not appear properly, you may need to rebuild your project templates. I took me a couple re-installs to get it right.
|||

did a re-install of the tool set which includes the BI templates and that worked.

Thanks!

can''t create reports via VS 2005 Standard

From what I read about the versions, VS 2005 Standard allows for SSRS development.

If I create a new project, I don't see the option to create anything from the BI section to create a report project.

I have SQL Server Express on my machine, and am able to run the SSRS configuartion management tool.

Do I have to run an .exe file or something?

Thanks!

When you installed SQL, did you expand all of the components and specify that you WANT them to be installed? For some reason they all default to do NOT intall.

I believe there is a component in client components (business intelligence studio) or something like that which actually installs the SQL server report project to Visual Studio.

Yes, Visual Studio comes with a menu in the create project wizard for Business Intelligence Projects. However, there are most likely no project types in that section for you, because the proper components were not installed when SQL was installed.

|||You have to install the SQL Server 2005 workstation tools including the Business Intelligence Studio AFTER VS 2005 is installed, and several new modules will show in the VS2005 startup splash, and new project types will be available.

If this still does not appear properly, you may need to rebuild your project templates. I took me a couple re-installs to get it right.
|||

did a re-install of the tool set which includes the BI templates and that worked.

Thanks!

Can't create Merge Publication

I have been trying for some time to create a Merge publication in SQL Server. I'm running SQL Server 2000 Standard Edition with the latest service pack on a Win2k3 Server. It doesn't seem to matter what replication-enabled database or which table I select
, I always get the same error at the end of the create publication wizard in Enterprise Mgr: "Error 2758 RAISERROR could not locate entry for error 21423 in sysmessages. Object 'pubs' (note: or whatever db I select) does not exist or is not a valid object
for this operation."
Any ideas here?
Corey - possibly this is an incomplete service pack install as some messages
in sysmessages are missing. You could have a look at sqlsp.log file from the
c:\windows directory which might shed some light on any failed actions
during the sp installation. Even if there isn't anything enlightening there
I'd reapply the sp3a.
HTH,
Paul Ibison
|||Thanks, Paul, but so far no luck. I dug through the log and didn't find anything all that revealing. I also re-applied SP3a, but that didn't help either. Still searching...
"Paul Ibison" wrote:

> Corey - possibly this is an incomplete service pack install as some messages
> in sysmessages are missing. You could have a look at sqlsp.log file from the
> c:\windows directory which might shed some light on any failed actions
> during the sp installation. Even if there isn't anything enlightening there
> I'd reapply the sp3a.
> HTH,
> Paul Ibison
>
>
|||Corey,
in htis case you could rebuild the master database or alternatively just add
the missing messages. To do the latter you'll need to create a linked server
to another server that has a complete master database and join to that table
(left outer join) to find the missing messages in sysmessages.
HTH,
Paul Ibison

Can't create databases in Management Studio

I seem to be having a number of problems using managment studio (MS) against my locally installed SQL 2005 Standard Edition. E.g. when I create a default database using MS it says...

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The server could not load DCOM. (Microsoft SQL Server, Error: 7404)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=7404&LinkId=20476

However, the hyperlinks are less than helpful. I also get problems doing various maintance work from MS. I don't think its a database engine problem 'cause I can do all the work via TSQL DDL but the interface is so much easier to use (or should be). BTW it's running on XP Pro (firewall problem?).

I've also found an Event Log entry but don't know what it's asking me to enable...

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17102
Date: 06/02/2006
Time: 20:12:06
User: N/A
Computer: TITAN
Description:
Failed to initialize Distributed COM (CoInitializeEx returned 80010119). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

|||

Finally sorted it out. It was the NVidia client to the motherboards Hardware Firewall that was causing the problem. I had to remove that to get IE7 working and now SQL Server is creating databases!

|||

I am getting all those exact same error messages when creating a database. My IE 7 is working just fine however. Can you tell me what you had to do to disable an nVidia motherboard hardware firewall thing? I've never heard of that, it sounds like it is worth a try at this point.

npack@.hotmail.com

|||Sure, you need to uninstall the nVidia firewall software.

Can't create databases in Management Studio

I seem to be having a number of problems using managment studio (MS) against my locally installed SQL 2005 Standard Edition. E.g. when I create a default database using MS it says...

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The server could not load DCOM. (Microsoft SQL Server, Error: 7404)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=7404&LinkId=20476

However, the hyperlinks are less than helpful. I also get problems doing various maintance work from MS. I don't think its a database engine problem 'cause I can do all the work via TSQL DDL but the interface is so much easier to use (or should be). BTW it's running on XP Pro (firewall problem?).

I've also found an Event Log entry but don't know what it's asking me to enable...

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17102
Date: 06/02/2006
Time: 20:12:06
User: N/A
Computer: TITAN
Description:
Failed to initialize Distributed COM (CoInitializeEx returned 80010119). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

|||

Finally sorted it out. It was the NVidia client to the motherboards Hardware Firewall that was causing the problem. I had to remove that to get IE7 working and now SQL Server is creating databases!

|||

I am getting all those exact same error messages when creating a database. My IE 7 is working just fine however. Can you tell me what you had to do to disable an nVidia motherboard hardware firewall thing? I've never heard of that, it sounds like it is worth a try at this point.

npack@.hotmail.com

|||Sure, you need to uninstall the nVidia firewall software.

Can't connect to sql server 2005 database using vb 2005 express

I've used Sql Server 2000 and Visual Studio 2003 for a few years. I've started a new position and they have access to Sql Server 2005 Standard and Visual Basic 2005 Express which I'd like to use for a new project. So I installed Sql Server 2005 and then VB 2005 Express on my workstation. I didn't choose the Sql Server option for VB Express because I already had Sql Server 2005 Standard installed with a simple database created. I created a simple vb project that justs connects to the database but I get the following error.

Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0000, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

I looked at permissions in the database and it looks ok. I'm the db owner and I'm using Windows Auth. My connection string is

"Data Source=MySystem;initial catalog=AdventureWorks;integrated security=true;"

I thought I'd look at the starter kit to get some ideas about what the problem is, but when I started the movie starter kit project, it was upset that I didn't have Sql Server 2005 EXPRESS installed. Yea, but I do have Sql Server 2005 Standard installed.

Any help will be greatly appreciated. Thanks.

If you're using Vista, make sure you add your account into SQL Server explicitly. Also check the SQL Server Surface Area Configuration tool to ensure your server accepts remote connections. Then make sure the server is listening on all ports using SQL Server Configuration Manager. There's a great tutorial in Books Online for connecting to SQL Server you can use to walk you through it.

Buck Woody

Can't Connect to SQL 2005 Using Remote Desktop and Local Administr

I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to the
server (no firewall involved) using Remote Desktop, I can't login to
Management Studio using the local administrator account. However, I can log
in using the domain administrator account. The local administrator account i
s
not locked out. I get the following error when trying to access Management
Studio using the local admin. account:
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (.Net SqlClient Data Provider)
Any ideas?***UPDATE***
Actually, it has nothing to do with remote connectivity. I tried to log in
to Management Studio locally as the local administrator, and it still
wouldn't let me and gave the same error. As mentioned previously, the domain
admin. works.
Thanks.
"Marks70" wrote:

> I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to th
e
> server (no firewall involved) using Remote Desktop, I can't login to
> Management Studio using the local administrator account. However, I can lo
g
> in using the domain administrator account. The local administrator account
is
> not locked out. I get the following error when trying to access Management
> Studio using the local admin. account:
> 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: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (.Net SqlClient Data Provider)
> Any ideas?

cant connect to server from another machine

Hi Friends
I have a sql server (2005 standard edition) on Win xp machine. i can connect to this server from my machine ok but others on the network try to connect i get following error

"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) "

but my remote connection allows remote connects. i also enabled "Named pipes" and "VIA" protocols under sql configuration manager but no avail.
any ideas on this one.
Thanks for your help.

Cheersyou need to config to enable this via surface area config tool|||Thanks for that and actually i tried that too but no avail.|||

Try disabling VIA, and restarting the SQL Server.

|||Peter
VIA is already disabled|||i also have sqlexpress on the same machine ,does it make any difference ?
BTW i stoped sqlexpress service but still made no difference!|||

The error you get most frequently indicates that TCP and/or Named Pipes are not enabled on the target SQL Server 2005.

The first thing is to make sure that these protocols are enables, and then restart the target SQL Server.

If you have SQL Server 2005 client tools installed on the remote client machine you can test the connection over TCP and Named Pipes, resp., by running the following commands:

sqlcmd -E -Stcp:<targetServer>

or

sqlcmd -E -Snp:<targetServer>

Notes:

- the switches -E -S are case sensitive, and must be in capital letters

- replace <targetMachine> with the name of the machine running the target SQL Server 2005.

If you still get errors their text may be helpful in troubleshooting further.

|||Peter
Thank you very much for your help.those 2 commands really helped.

first command (uses tcp) it connected ok but 2nd command(using np) gave an error.
so on target server i enabled Named pipes and restarted server and tried to connect again from remote machine and guess what it connect nicely. and now i can connect to target server from my report manager page also which was originally giving problem.
Thanks again for your help :)

one question remained though we've another sql server on a different machine which has too only TCP/IP enabled but all other PCs in the network able to connect without any problem!!

why my PC was any different ?
Thanks|||

How does your application specify the server in the connection string?

If it uses an alias, does the alias specify Named Pipes as the protocol? Is there any chance the connection string specifies the Named Pipes protocol through the "Network Library" or "Net" property, e.g. as "Network Library=dbnmpntw"?

|||Peter
here my application is Report Manager page (http://localhost/reportserver) and connection does not specify any protocols.

we installed sql server with default settings so i dont think there is any alias|||

I have had identical connection problem problems. The two commands are extremely helpful for diagnosis. I wish I had known them earlier. Thank you!

No matter what I try (enabling, disabling, stopping, restarting, ...), I cannot get TCP work, but the name pipes can be made work easily and I can certainly live with it.

hz

|||

Hi all

I am fascinated by this discussion. I have had similar problems.

I have access to 100 computers in the university library on the same network. Each pc is running Windows XP and has a copy os SQL Server 2005 installed (the full version and express).

I am manually connecting servers (but would love to know how to in T-SQL as well ;-)). A friend has helped me before, and we disabled Named Pipes and enabled TCPIP on some of the computers. We were then able to use the wizzard to connect these computers. I am using SQL Server Authentication, and each database, and all connections are using the same login, and I have set this up to have server role "svsadmin".

Unfortunately this does not work now. I have followed the instructions suggested above (and enabled both TCPIP and Named Pipes), and now, while I am able to connect the servers on different machines, the connected server does not have an icon that indicates that it is either

* started (green triangle) or

* stopped (red triangle)

but an empty little circle at the base of the satabase cream cylinder

I hope I have given the right amount of info.

Thanks in advance.

Greg

|||

Greg

did you mean ,you cant see whether "server" running or not ?

if so "sql server configuration manager" under configuration tools you should be able to see whether sql server running or not.

BTW if you dont use sqlexpress i suggest you uninstall it as it resolved many issues for me.i guess sql server 2005 and sqlexpress conflicting each other!

|||

Hi

Thanks for the response.

I have uninstalled SQL Server Express on 2 of the machines.

The servers are running - I'm sure of that, but unbelievably slowly. I have been able to view (in SQL Server Managment Studio) the contents of tables on either the local or networked server. (The server status is still being denoted by the empty white disc superimposed on the yellow server cylinder...)

So they must be running right? The SQL Server Configuration Manager agrees - but to me the server manager is telling me that the server is running locally, which is the case. The problem relates to the connected database...

Despite deleting the database, unfortunately still getting this unusual situation. I'm able to explore a database on either server from either computer once I have connected the servers. But unfortunately I can not use T-SQL to input into a table on the networked server. (I am using sp_addlinkedserver to link the server successfully.)

Could the problem be a network setting, and if so, what should I ask the network administrator to change?

Thanks

Greg

|||

am out of ideas on this Greg.

BTW after uninstalling sqlexpress have you restarted machines ?

if not give it a try and see .

cant connect to server from another machine

Hi Friends
I have a sql server (2005 standard edition) on Win xp machine. i can connect to this server from my machine ok but others on the network try to connect i get following error

"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) "

but my remote connection allows remote connects. i also enabled "Named pipes" and "VIA" protocols under sql configuration manager but no avail.
any ideas on this one.
Thanks for your help.

Cheersyou need to config to enable this via surface area config tool|||Thanks for that and actually i tried that too but no avail.|||

Try disabling VIA, and restarting the SQL Server.

|||Peter
VIA is already disabled|||i also have sqlexpress on the same machine ,does it make any difference ?
BTW i stoped sqlexpress service but still made no difference!|||

The error you get most frequently indicates that TCP and/or Named Pipes are not enabled on the target SQL Server 2005.

The first thing is to make sure that these protocols are enables, and then restart the target SQL Server.

If you have SQL Server 2005 client tools installed on the remote client machine you can test the connection over TCP and Named Pipes, resp., by running the following commands:

sqlcmd -E -Stcp:<targetServer>

or

sqlcmd -E -Snp:<targetServer>

Notes:

- the switches -E -S are case sensitive, and must be in capital letters

- replace <targetMachine> with the name of the machine running the target SQL Server 2005.

If you still get errors their text may be helpful in troubleshooting further.

|||Peter
Thank you very much for your help.those 2 commands really helped.

first command (uses tcp) it connected ok but 2nd command(using np) gave an error.
so on target server i enabled Named pipes and restarted server and tried to connect again from remote machine and guess what it connect nicely. and now i can connect to target server from my report manager page also which was originally giving problem.
Thanks again for your help :)

one question remained though we've another sql server on a different machine which has too only TCP/IP enabled but all other PCs in the network able to connect without any problem!!

why my PC was any different ?
Thanks|||

How does your application specify the server in the connection string?

If it uses an alias, does the alias specify Named Pipes as the protocol? Is there any chance the connection string specifies the Named Pipes protocol through the "Network Library" or "Net" property, e.g. as "Network Library=dbnmpntw"?

|||Peter
here my application is Report Manager page (http://localhost/reportserver) and connection does not specify any protocols.

we installed sql server with default settings so i dont think there is any alias|||

I have had identical connection problem problems. The two commands are extremely helpful for diagnosis. I wish I had known them earlier. Thank you!

No matter what I try (enabling, disabling, stopping, restarting, ...), I cannot get TCP work, but the name pipes can be made work easily and I can certainly live with it.

hz

|||

Hi all

I am fascinated by this discussion. I have had similar problems.

I have access to 100 computers in the university library on the same network. Each pc is running Windows XP and has a copy os SQL Server 2005 installed (the full version and express).

I am manually connecting servers (but would love to know how to in T-SQL as well ;-)). A friend has helped me before, and we disabled Named Pipes and enabled TCPIP on some of the computers. We were then able to use the wizzard to connect these computers. I am using SQL Server Authentication, and each database, and all connections are using the same login, and I have set this up to have server role "svsadmin".

Unfortunately this does not work now. I have followed the instructions suggested above (and enabled both TCPIP and Named Pipes), and now, while I am able to connect the servers on different machines, the connected server does not have an icon that indicates that it is either

* started (green triangle) or

* stopped (red triangle)

but an empty little circle at the base of the satabase cream cylinder

I hope I have given the right amount of info.

Thanks in advance.

Greg

|||

Greg

did you mean ,you cant see whether "server" running or not ?

if so "sql server configuration manager" under configuration tools you should be able to see whether sql server running or not.

BTW if you dont use sqlexpress i suggest you uninstall it as it resolved many issues for me.i guess sql server 2005 and sqlexpress conflicting each other!

|||

Hi

Thanks for the response.

I have uninstalled SQL Server Express on 2 of the machines.

The servers are running - I'm sure of that, but unbelievably slowly. I have been able to view (in SQL Server Managment Studio) the contents of tables on either the local or networked server. (The server status is still being denoted by the empty white disc superimposed on the yellow server cylinder...)

So they must be running right? The SQL Server Configuration Manager agrees - but to me the server manager is telling me that the server is running locally, which is the case. The problem relates to the connected database...

Despite deleting the database, unfortunately still getting this unusual situation. I'm able to explore a database on either server from either computer once I have connected the servers. But unfortunately I can not use T-SQL to input into a table on the networked server. (I am using sp_addlinkedserver to link the server successfully.)

Could the problem be a network setting, and if so, what should I ask the network administrator to change?

Thanks

Greg

|||

am out of ideas on this Greg.

BTW after uninstalling sqlexpress have you restarted machines ?

if not give it a try and see .

Can't connect to default database

I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
Wendy
Run the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:

>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy

Can't connect to default database

I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy

Can't connect to default database

I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:

>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I ge
t
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an erro
r
>occurred during the login process (provider shared memory provider error 0
-
>no process is on the other end of the pipe). Microsoft SQL Server error 233
.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy

Can''t connect to a sql express on a workgroup pc

Hi Guys,

I'm trying to connect to a sql express on a workgroup PC through sql server 2005 standard edition remotely but i can't.

I have checked and make sure that tcp/ip and other protocals are allowed. There is no firewall on both PCs and the sql browser service is running as well.
Somehow i can connect using the IP address but not the name?

Any idea why?

TA

Gemma

post back the error

Madhu

|||

HI Madhu,

Here it is:

TITLE: Connect to Server

Cannot connect to TYPICAL1.

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

BUTTONS:

OK

Ta

Gemma

|||

check this out

http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

Madhu

Can't connect Report server at management studio and report manager at Explorer

I am using 2003 Server standard Edition (5.2.3790), SQL SERVER 2005 (9.00.1399) and IIS 6.0

When I tried to open the report manger at Explorer as typed http://servername/reports, http://localhost/reports, http://127.0.0.1/reports

I got an error : HTTP 404 : file not found

At testing connection on SQL server management studio, got an error -> the request failed with HTTP 404 status (Microsoft.sqlserver.management.UI.RSClient)

My configuration details as belows;

1. IIS 6.0 configuration

I made reports and reportserver virtual directory on Default web sites.

<<Default web site>>

Web site > Port 80, IP address : all unassigned

Directory security > checked Enable anonymous access

<< Report manager>>

Virtual directory >C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager

ASP.net -> C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\web.config

(enable default content pages : home.aspx)

Directory Security > checked at Integrated Windows Authentication

<<Report server>>

Virtual directory > C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

ASP.net -> C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config

(enable default content pages : default.aspx, default.htm.default.asp, index.htm,iisstart.htm)

Directory Security > checked at Integrated Windows Authentication

2. Report server configuration

<<RSWebApplication.config>> file

<UI>
<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>Reportserver</ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

<<rsreportserver.config>> file

<Service>
<UrlRoot>http://<servername>/reportserver</UrlRoot>
<UserName></UserName>
<Password></Password>
<PolicyLevel>rssrvpolicy.config</PolicyLevel>
<WebServiceAccount>NT Authority\NetworkService</WebServiceAccount>
<IsWebServiceEnabled>True</IsWebServiceEnabled>
</Service>

3. SQL Server Management studio configuration

Authentication : Window Authentication

Please help me out. Should I reinstalled reporting service into SQL SERVER 2005?

thanks,

Eunsu

The URL you want to connect to is http://servername/reportserver.

|||Sure, I also tried to connect reportserver by url http://servername/reportserver, but got the same error.|||

Have you tried running the configuration tool? It should walk you through making sure that the server is properly configured.

Start->Microsoft SQL Server 2005->Configuration Tools->Reporting Services Configuration

|||

In advance, thanks for your concern

I've already done by reporting service configuration tool and checked every condition that was OK. But the result was same error messages.

Do I reinstall reporting service ?