MSDE SP3a and XP SP2 on Localhost

I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:

> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:

> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql

MSDE local host failure

Why would the localhost not install but rather our named instance will
install? We have an inconsistent problem with installations. Our app
depends on a named instance and a secondary app depends on local host
so we need both. However, systems that have previous installed,
uninstalled and try to reinstall the current app, only the local host
will install or the named instance will install, but not both. This
doesn't happen on all machines either. We encounter the usual errors
as seen in this group such as 'server not found', etc. and I can
usually get MSDE installed only if after I uninstall, I delete the MSDE
references in the registry. Yet I am baffled how MSDE would install
the named instance but not the local. This has primarily been occuring
on XP sp2 machines and all data resides on the client machine where
MSDE is installed.
Any suggestions?
Thanks.
hi,
Colleen wrote:
> Why would the localhost not install but rather our named instance will
> install? We have an inconsistent problem with installations. Our app
> depends on a named instance and a secondary app depends on local host
> so we need both. However, systems that have previous installed,
> uninstalled and try to reinstall the current app, only the local host
> will install or the named instance will install, but not both. This
> doesn't happen on all machines either. We encounter the usual errors
> as seen in this group such as 'server not found', etc. and I can
> usually get MSDE installed only if after I uninstall, I delete the
> MSDE references in the registry. Yet I am baffled how MSDE would
> install the named instance but not the local. This has primarily
> been occuring on XP sp2 machines and all data resides on the client
> machine where MSDE is installed.
just to test, I installed 2 additional named instances of MSDE (sp3 and sp4)
on a pc hosting 1 deafault instance of MSDE sp4...
and I am unable to reproduce the problem... of course, uninstalling an
instance requires you to manually clean the file system, or manually remove
all file system and windows registry entries...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply