Can SQL tools be installed from server install?

Good day,

Can SQL Server tools (QA, EM) can be installed on a client machine from
a full SQL Server installation on a server? I can't find the CD.

Thanks for your time.
EricEric Bragas (ericbragas@.yahoo.com) writes:
> Can SQL Server tools (QA, EM) can be installed on a client machine from
> a full SQL Server installation on a server? I can't find the CD.

Probably, but you would have to spend some time registering DLLs etc,
and it would be quite messy.

So finding the CD is a good idea.

If you are an MSDN Universal Subscribler, you can get it from MSDN
Downloads.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||If you have a copy of SQL 2000 Enterprise Edition Eval copy, you can load it
from there. The tools will not expire, just make sure you only select
client tools and not the database engine

Akinja Richards

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9686B453DA798Yazorman@.127.0.0.1...
> Eric Bragas (ericbragas@.yahoo.com) writes:
>> Can SQL Server tools (QA, EM) can be installed on a client machine from
>> a full SQL Server installation on a server? I can't find the CD.
> Probably, but you would have to spend some time registering DLLs etc,
> and it would be quite messy.
> So finding the CD is a good idea.
> If you are an MSDN Universal Subscribler, you can get it from MSDN
> Downloads.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||Akinja (akinja@.sbcglobal.net) writes:
> If you have a copy of SQL 2000 Enterprise Edition Eval copy, you can
> load it from there. The tools will not expire, just make sure you only
> select client tools and not the database engine

And if you don't have it, you can download it from www.microsoft.com.

There might be two issues:
1) License may not permit connecting to production environments.
2) It used to be that service packs can be applied to EvalEdition. I
don't know if this still is the case.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||I think MS has smart to that trick. I haven't tried it.

Akinja

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9686EB719AA49Yazorman@.127.0.0.1...
> Akinja (akinja@.sbcglobal.net) writes:
>> If you have a copy of SQL 2000 Enterprise Edition Eval copy, you can
>> load it from there. The tools will not expire, just make sure you only
>> select client tools and not the database engine
> And if you don't have it, you can download it from www.microsoft.com.
> There might be two issues:
> 1) License may not permit connecting to production environments.
> 2) It used to be that service packs can be applied to EvalEdition. I
> don't know if this still is the case.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp

Can SQL Server 2005 Express and MSDE CoExist?

I read in the installation requirements document for SQL Server 2005 Express the section on upgrading MSDE to SQL Server 2005 Express. The section indicated that if MSDE is installed via an application installation, that application will have to be uninstalled to remove MSDE. This leads to my question.

The small application I'm looking into developing will require SQL Server 2005 Express. What if a customer is using an application that installed MSDE? Can the two products coexist without problems?

Thanks!!

hi,

yes, MSDE 2000 and SQLExpress can coexists...

SQLExpress installation will upgrade the installed COM based binaries (SQL-DMO) to SQL Server 2005 level, but they have been tested to be retro-compatible and I'm personally not aware of troubles in this area..

regards

Can SQL Express 2005 & MSDE reside on the same box?

Is the installation of MSDE and SQL Express 2005 on the same computer a supported configuration?

Many thanks

Yes, you can run Express and MSDE/WMSDE in the same machine using different instance names.

Can Sql 2000 and Sql 2005 exist on same server?

My instructions are to install Sql 2005 on server BIGPETE2. I found that there was already an installation of Sql 2000, with databases that I was quite sure should remain as SQL 2000.

According to info I found on the internet, it should be possible to have separate instances of 2000 and 2005, so I went ahead and tried to install, giving the 2005 version a different name, BIGPETE2005. It didn't hit me with any error messages, but neither did it install a different database server. When I was finished, I was able to open Management Studio, but the only database server it could find to open was BIGPETE2, which is not what I wanted.

Enterprise Manager still works, and the mdf dates haven't updated, so I'm guessing the data is still safe, but I need both servers up and running.

Okay, I just read through the installation report, and I saw this:

Service pack requirement check:

Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

1. What service pack is it asking for?

2. And doesn't that imply that it's upgrading my Sql 2000 installation instead of installing a new instance of Sql 2005?

In Management Studio, you will be able to connect to both instances. To connect to your SQL 2005 instance, you'll need to supply machine name / instance name (ex: MACHINE/BIGPETE2005).

Thanks,
Sam Lester (MSFT)

|||How do you connect to both instances in SQL 2005? Can we have a step by step with screen shots? Are any other modules needed such as the backwards compatibility module?

Can Reporting Services use IIS on another server?

Reporting Services on SQL 2005 says that I must install IIS (its an
installation prerequisite). Well, I really don't want to put IIS on a
production SQL Server. I like IIS, but it certainly exposes a lot more
potential security holes on the server because any website hosting product
is always a security risk to that machine. Besides, my SQL Server is not
exposed to the internet like my web servers, so I don't quite get why I
would even want IIS on the SQL Server.
I want to use Reporting Services, though. Can I somehow use Reporting
Services against IIS on another server? I'm not describing it well because
I've never used Reporting Services and I don't know if it, too, would be on
the other server, or what. Can someone guide me as to my options here, and
what to install where to keep the SQL Server machine more secure and stable
but still have Reporting Services capabilities? Thank you.Yes. You can install Reporting Services on an application (web) server
apart from your SQL database server. In fact, this is a very common
installation technique. Install and configure IIS on the desired server. I
strongly recommend having a certificate on that server. You can then
install Reporting Services 2005 on that server. Once it is installed, you
can configure it to use your production SQL server for its back-end
databases using the Reporting Services Configuration tool.
I have two suggestions for getting started. One, build a throwaway test
server to do your first testing and deployment on. Second, purchase a good
book on Reporting Services. Both will save you a lot of headaches.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"HK" <replywithingroup@.notreal.com> wrote in message
news:RIzWf.19201$%d.2027@.tornado.socal.rr.com...
> Reporting Services on SQL 2005 says that I must install IIS (its an
> installation prerequisite). Well, I really don't want to put IIS on a
> production SQL Server. I like IIS, but it certainly exposes a lot more
> potential security holes on the server because any website hosting product
> is always a security risk to that machine. Besides, my SQL Server is not
> exposed to the internet like my web servers, so I don't quite get why I
> would even want IIS on the SQL Server.
> I want to use Reporting Services, though. Can I somehow use Reporting
> Services against IIS on another server? I'm not describing it well
> because
> I've never used Reporting Services and I don't know if it, too, would be
> on
> the other server, or what. Can someone guide me as to my options here,
> and
> what to install where to keep the SQL Server machine more secure and
> stable
> but still have Reporting Services capabilities? Thank you.
>|||and what book would be a good book, Geoff?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:ekzZm91UGHA.5660@.TK2MSFTNGP12.phx.gbl...
> Yes. You can install Reporting Services on an application (web) server
> apart from your SQL database server. In fact, this is a very common
> installation technique. Install and configure IIS on the desired server.
> I strongly recommend having a certificate on that server. You can then
> install Reporting Services 2005 on that server. Once it is installed, you
> can configure it to use your production SQL server for its back-end
> databases using the Reporting Services Configuration tool.
> I have two suggestions for getting started. One, build a throwaway test
> server to do your first testing and deployment on. Second, purchase a
> good book on Reporting Services. Both will save you a lot of headaches.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:RIzWf.19201$%d.2027@.tornado.socal.rr.com...
>> Reporting Services on SQL 2005 says that I must install IIS (its an
>> installation prerequisite). Well, I really don't want to put IIS on a
>> production SQL Server. I like IIS, but it certainly exposes a lot more
>> potential security holes on the server because any website hosting
>> product
>> is always a security risk to that machine. Besides, my SQL Server is
>> not
>> exposed to the internet like my web servers, so I don't quite get why I
>> would even want IIS on the SQL Server.
>> I want to use Reporting Services, though. Can I somehow use Reporting
>> Services against IIS on another server? I'm not describing it well
>> because
>> I've never used Reporting Services and I don't know if it, too, would be
>> on
>> the other server, or what. Can someone guide me as to my options here,
>> and
>> what to install where to keep the SQL Server machine more secure and
>> stable
>> but still have Reporting Services capabilities? Thank you.
>>
>|||Since I haven't seen an update to "Hitchhikers Guide to SQL Server 2000
Reporting Services" by Peter BlackBurn and William Vaughn, I will have to go
with "Microsoft SQL 2005 Reporting Services" by Brian Larson. It was
written against the beta release which was very close to the production
version, and is geared towards the beginning Reporting Services user. I
think there is a BI/Reporting Services volume forthcoming for the "Inside
SQL Server 2005" series, but I haven't seen a formal announcement yet.
Amazon has several other volumes in this series available for pre-order.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <me@.isp.net> wrote in message news:fDDWf.8879$Ph4.1246@.edtnps90...
> and what book would be a good book, Geoff?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:ekzZm91UGHA.5660@.TK2MSFTNGP12.phx.gbl...
>> Yes. You can install Reporting Services on an application (web) server
>> apart from your SQL database server. In fact, this is a very common
>> installation technique. Install and configure IIS on the desired server.
>> I strongly recommend having a certificate on that server. You can then
>> install Reporting Services 2005 on that server. Once it is installed,
>> you can configure it to use your production SQL server for its back-end
>> databases using the Reporting Services Configuration tool.
>> I have two suggestions for getting started. One, build a throwaway test
>> server to do your first testing and deployment on. Second, purchase a
>> good book on Reporting Services. Both will save you a lot of headaches.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:RIzWf.19201$%d.2027@.tornado.socal.rr.com...
>> Reporting Services on SQL 2005 says that I must install IIS (its an
>> installation prerequisite). Well, I really don't want to put IIS on a
>> production SQL Server. I like IIS, but it certainly exposes a lot more
>> potential security holes on the server because any website hosting
>> product
>> is always a security risk to that machine. Besides, my SQL Server is
>> not
>> exposed to the internet like my web servers, so I don't quite get why I
>> would even want IIS on the SQL Server.
>> I want to use Reporting Services, though. Can I somehow use Reporting
>> Services against IIS on another server? I'm not describing it well
>> because
>> I've never used Reporting Services and I don't know if it, too, would be
>> on
>> the other server, or what. Can someone guide me as to my options here,
>> and
>> what to install where to keep the SQL Server machine more secure and
>> stable
>> but still have Reporting Services capabilities? Thank you.
>>
>>
>|||thanks Geoff
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23rccjA4UGHA.4792@.TK2MSFTNGP14.phx.gbl...
> Since I haven't seen an update to "Hitchhikers Guide to SQL Server 2000
> Reporting Services" by Peter BlackBurn and William Vaughn, I will have to
> go with "Microsoft SQL 2005 Reporting Services" by Brian Larson. It was
> written against the beta release which was very close to the production
> version, and is geared towards the beginning Reporting Services user. I
> think there is a BI/Reporting Services volume forthcoming for the "Inside
> SQL Server 2005" series, but I haven't seen a formal announcement yet.
> Amazon has several other volumes in this series available for pre-order.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <me@.isp.net> wrote in message news:fDDWf.8879$Ph4.1246@.edtnps90...
>> and what book would be a good book, Geoff?
>> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>> news:ekzZm91UGHA.5660@.TK2MSFTNGP12.phx.gbl...
>> Yes. You can install Reporting Services on an application (web) server
>> apart from your SQL database server. In fact, this is a very common
>> installation technique. Install and configure IIS on the desired
>> server. I strongly recommend having a certificate on that server. You
>> can then install Reporting Services 2005 on that server. Once it is
>> installed, you can configure it to use your production SQL server for
>> its back-end databases using the Reporting Services Configuration tool.
>> I have two suggestions for getting started. One, build a throwaway test
>> server to do your first testing and deployment on. Second, purchase a
>> good book on Reporting Services. Both will save you a lot of headaches.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:RIzWf.19201$%d.2027@.tornado.socal.rr.com...
>> Reporting Services on SQL 2005 says that I must install IIS (its an
>> installation prerequisite). Well, I really don't want to put IIS on a
>> production SQL Server. I like IIS, but it certainly exposes a lot more
>> potential security holes on the server because any website hosting
>> product
>> is always a security risk to that machine. Besides, my SQL Server is
>> not
>> exposed to the internet like my web servers, so I don't quite get why I
>> would even want IIS on the SQL Server.
>> I want to use Reporting Services, though. Can I somehow use Reporting
>> Services against IIS on another server? I'm not describing it well
>> because
>> I've never used Reporting Services and I don't know if it, too, would
>> be on
>> the other server, or what. Can someone guide me as to my options here,
>> and
>> what to install where to keep the SQL Server machine more secure and
>> stable
>> but still have Reporting Services capabilities? Thank you.
>>
>>
>>
>

Can not start tcp port 1433 on MSDE

I've got an installation of MSDE that insists on only allowing shared memory
access. This works fine but I would like to access th db via tcp. I have
ran SVRNETCN.exe and verified that TCP is selected. I have even verified
that the port number etc. is set in the registry. It just refuses to
avtivate tcp when I restart MSDE or the box it's runinning on.
Here's the errorlog:
2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
(Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-30 00:03:33.20 server All rights reserved.
2004-04-30 00:03:33.20 server Server Process ID is 4416.
2004-04-30 00:03:33.20 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2004-04-30 00:03:33.30 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-04-30 00:03:33.38 server SQL Server configured for thread mode
processing.
2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
2004-04-30 00:03:35.55 spid3 Recovery complete.
Where in that log do you see evidence of SQL Server "refusing to activate
tcp"? Did you really mean, "I can't connect to SQL Server on port 1433"?
If so, I would check your network/router/firewall settings before assuming
the problem is service- or machine-specific.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Karl Foley" <karl@.thefoleyhouse.co.uk> wrote in message
news:e3R9sIkLEHA.2456@.TK2MSFTNGP12.phx.gbl...
> I've got an installation of MSDE that insists on only allowing shared
> memory
> access. This works fine but I would like to access th db via tcp. I have
> ran SVRNETCN.exe and verified that TCP is selected. I have even verified
> that the port number etc. is set in the registry. It just refuses to
> avtivate tcp when I restart MSDE or the box it's runinning on.
> Here's the errorlog:
> 2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
> (Intel X86)
> Nov 29 2003 20:52:47
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
> 2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-30 00:03:33.20 server All rights reserved.
> 2004-04-30 00:03:33.20 server Server Process ID is 4416.
> 2004-04-30 00:03:33.20 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
> 2004-04-30 00:03:33.30 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-04-30 00:03:33.38 server SQL Server configured for thread mode
> processing.
> 2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
> 2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
> 2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
> 2004-04-30 00:03:34.21 server SQL Server is ready for client
> connections
> 2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
> 2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
> 2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
> 2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
> 2004-04-30 00:03:35.55 spid3 Recovery complete.
>
>
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%237IBIxnLEHA.2592@.tk2msftngp13.phx.gbl...
> Where in that log do you see evidence of SQL Server "refusing to activate
> tcp"?
Thanks for the offer of help, I'm just abut ready to give up on this!
Just about here:
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
You can see it's only using shared memory.

> Did you really mean, "I can't connect to SQL Server on port 1433"?
> If so, I would check your network/router/firewall settings before assuming
> the problem is service- or machine-specific.
No. I've tried to read all the posts on here regarding the problem and have
done multiple searches on google to try and solve this problem. No matter
what I do, MSDE will not listen on TCP port 1433. Here's a quick snip of
the output of netstat -an:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING
[Snip]
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1533 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
[Snip]
As you can see, no port 1433 is listening here. I have only tried
connecting to port 1433 from this machine but can't see the point of trying
another machine if I can see the port is not open. This machine does not
have any firewall software enabled\installed on it. That functionality is
being provided by a hardware device.
As the version of MSDE seems so much newer than anything else I've seen
posted I am beginning to wonder if it is some kind of security feature...
|||> As the version of MSDE seems so much newer
Yes, 880 is quite a recent patch. Care to share where you obtained it?
Anyway, run svrnetcn.exe (it should execute from command line just like
that, otherwise it's in SQL Server's Tools\Binn folder) and make sure TCP/IP
is on the enabled side. If it isn't, move it over, hit apply, and restart
SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
Make sure hide server is unchecked, then try changing the default TCP port
to some other number, hit apply, restart SQL Server, then change the default
TCP port back to 1433, hit apply, and restart SQL Server.
If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
just for fun, and then see http://support.microsoft.com/?id=306865 for a
registry setting that may need a fix.
If this is the way it has worked since you installed MSDE, you might
consider uninstalling and reinstalling (from SP3a) making sure to set
DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
leads me to believe that installing from scratch would be the cleanest
solution anyway... sometimes these one-off patches have various side effects
that simply haven't been tested (which is why they are typically not
announced and readily available to the masses).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||You might also need to check to see if it is truly MSDE or is it WMSDE.. If
it is WMSDE it can only be accessed from the same machine. Based on the
instance name of SharePoint I would assume that it is really WMSDE..
http://www.microsoft.com/resources/d...us/stsf17.mspx
If you need to access/use it for other purposes and/or from other machines
you will need to upgrade the instance to full SQL server.. or another
possible option would be to use a different instance of MSDE for your other
needs.

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:u0HZpsyLEHA.2148@.TK2MSFTNGP09.phx.gbl...
> Yes, 880 is quite a recent patch. Care to share where you obtained it?
> Anyway, run svrnetcn.exe (it should execute from command line just like
> that, otherwise it's in SQL Server's Tools\Binn folder) and make sure
TCP/IP
> is on the enabled side. If it isn't, move it over, hit apply, and restart
> SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
> Make sure hide server is unchecked, then try changing the default TCP port
> to some other number, hit apply, restart SQL Server, then change the
default
> TCP port back to 1433, hit apply, and restart SQL Server.
> If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
> just for fun, and then see http://support.microsoft.com/?id=306865 for a
> registry setting that may need a fix.
> If this is the way it has worked since you installed MSDE, you might
> consider uninstalling and reinstalling (from SP3a) making sure to set
> DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
> leads me to believe that installing from scratch would be the cleanest
> solution anyway... sometimes these one-off patches have various side
effects
> that simply haven't been tested (which is why they are typically not
> announced and readily available to the masses).
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
|||"David Copeland [MSFT]" <davidcop@.online.microsoft.com> wrote in message
news:e7Aoio6LEHA.3216@.TK2MSFTNGP12.phx.gbl...
> You might also need to check to see if it is truly MSDE or is it WMSDE..
If
> it is WMSDE it can only be accessed from the same machine. Based on the
> instance name of SharePoint I would assume that it is really WMSDE..
Fantastic - That's exactly it.
I installed another instance of MSDE and this runs perfectly over TCP port
1433 as expected. I found it confusing because:
I didn't know that WMSDE was a different product to MSDE or that WMSDE
indeed even existed.
The tools are all there to enable network connectivity even though WMSDE
doesn't use them.
Thanks everyone.

Can not install Service Pack 3a

When I try to install SQL SP3a, I get error from my
server: "A previous program installation created pending
file operations. You must restart youe computer." After I
restart my PC, I still get the same error when I try to
install SQL SP3a.
Are there any suggestion to help me to install SP 3a?
Thanks,
-Mike
Have a look here
http://www.tkdinesh.com/faq/ans/pendingfiles.html
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Mike Torry" <anonymous@.discussions.microsoft.com> wrote in message
news:a40201c43522$7633c140$a001280a@.phx.gbl...
> When I try to install SQL SP3a, I get error from my
> server: "A previous program installation created pending
> file operations. You must restart youe computer." After I
> restart my PC, I still get the same error when I try to
> install SQL SP3a.
> Are there any suggestion to help me to install SP 3a?
> Thanks,
> -Mike

Can not install Service Pack 3a

When I try to install SQL SP3a, I get error from my
server: "A previous program installation created pending
file operations. You must restart youe computer." After I
restart my PC, I still get the same error when I try to
install SQL SP3a.
Are there any suggestion to help me to install SP 3a?
Thanks,
-MikeHave a look here
http://www.tkdinesh.com/faq/ans/pendingfiles.html
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Mike Torry" <anonymous@.discussions.microsoft.com> wrote in message
news:a40201c43522$7633c140$a001280a@.phx.gbl...
> When I try to install SQL SP3a, I get error from my
> server: "A previous program installation created pending
> file operations. You must restart youe computer." After I
> restart my PC, I still get the same error when I try to
> install SQL SP3a.
> Are there any suggestion to help me to install SP 3a?
> Thanks,
> -Mike

Can not install Service Pack 3a

When I try to install SQL SP3a, I get error from my
server: "A previous program installation created pending
file operations. You must restart youe computer." After I
restart my PC, I still get the same error when I try to
install SQL SP3a.
Are there any suggestion to help me to install SP 3a?
Thanks,
-MikeHave a look here
http://www.tkdinesh.com/faq/ans/pendingfiles.html
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Mike Torry" <anonymous@.discussions.microsoft.com> wrote in message
news:a40201c43522$7633c140$a001280a@.phx.gbl...
> When I try to install SQL SP3a, I get error from my
> server: "A previous program installation created pending
> file operations. You must restart youe computer." After I
> restart my PC, I still get the same error when I try to
> install SQL SP3a.
> Are there any suggestion to help me to install SP 3a?
> Thanks,
> -Mike