I am using crystal report for reporting in my application but in some computers the application does not show the export option in Excel, i export mostly in excel for reporting but this problem occurs in some computers rest of the computers are exporting normaly i have already installed MDAC 2.8 but could not solve that problem is there any solution then please let me know thanks.Each Export format (Excel, pdf, etc) and each Export Destination (Aplication, Disk, etc) has to have a dll installed on the machine it's running on. If, for example, you can export to pdf, but not to Excel, your problem may be that the dll required for Excel Export is missing.
In Crystal Reports 8.5, there's a file called runtime.hlp that tells exactly what dlls are required depending on what your application uses.
(Ex. For CR 8.5 and Win2k, my Excel export dll is: C:\WINNT\Crystal\u2fxls.dll and my dll for Exporting to Application is: C:\WINNT\Crystal\u2dapp.dll)sql
Showing posts with label computers. Show all posts
Showing posts with label computers. Show all posts
Thursday, March 29, 2012
Tuesday, February 14, 2012
cannot connect to named instance of msde
I installed a named instance of MSDE SP4. It seemed to go OK, and no errors
were reported.
The instance is listed in the computer's services, and it is running.
However, neither the computer name nor the new MSDE instance is listed in
the SQL Server Service Manager (although an instance on a networked computer
is listed). And I cannot connect via osql.
Any suggestions?
hi Paul,
Paul Pedersen wrote:
> I installed a named instance of MSDE SP4. It seemed to go OK, and no
> errors were reported.
> The instance is listed in the computer's services, and it is running.
> However, neither the computer name nor the new MSDE instance is
> listed in the SQL Server Service Manager (although an instance on a
> networked computer is listed). And I cannot connect via osql.
> Any suggestions?
if you can not connect from remote client, it can be depending on disabled
network protocols (default for MSDE installation, you can bypass at install
time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
time, using the Server Network Utility [svrnetcn.exe] to enable the
desired/required network protocol) or, for instance, firewall/network
problems (Windows XP sp2 Firewall requires to provide an exception for the
service or to the port)..
as you are reporting the SQL Server Service Manager does not list the
instances, I'd guess it's becouse the very first scenario
(http://support.microsoft.com/default...b;EN-US;814132)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||That did the trick. Thank you!
Is there some reason that disabling the protocols is the default? It seems
to me that without that, MSDE is completely unusable. Like I said before, I
couldn't even get osql to connect. Maybe that's a different problem.
One note: the Server Network Utility says that changes will take effect
after the service is restarted, but restarting MSDE didn't make it work. I
had to reboot the computer
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
> install time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later,
> at run time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> That did the trick. Thank you!
> Is there some reason that disabling the protocols is the default? It
> seems to me that without that, MSDE is completely unusable. Like I
> said before, I couldn't even get osql to connect. Maybe that's a
> different problem.
actually not... Microsoft provided a setup that should protect all "passive"
users from external malicious attacks (think of Slammer and the like) only
enabling trusted WinNT connections and disabling network protocols ...
and this is not a bad idea... always give the least required privilege
pattern :D:D
> One note: the Server Network Utility says that changes will take
> effect after the service is restarted, but restarting MSDE didn't
> make it work. I had to reboot the computer
stopping and restarding the service is usually enonght thought...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks again.
It took a fair amount of trial before I realized that to connect to a named
MSDE instance with osql, you have to preface the name with server\, even if
it's on the same machine.
Only one problem left. In testing, I uninstalled and reinstalled with
DISABLENETWORKPROTOCOLS=0. But the instance does not show up on the network.
In other words, I installed MSDE on Machine A. The Service Manager on
Machine A can see its own server, plus an instance of SQL Server on Machine
B. Machine B can see its own SQL Server instance, but cannot see the MSDE
instance on Machine A.
On Machine A, the Network Utility says the tcp/ip default port is 1059 (must
be some default, because I did not set it), and Hide Server is not checked.
Do you have suggestions about this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hk1c1Fhii6nU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> actually not... Microsoft provided a setup that should protect all
> "passive" users from external malicious attacks (think of Slammer and the
> like) only enabling trusted WinNT connections and disabling network
> protocols ...
> and this is not a bad idea... always give the least required privilege
> pattern :D:D
>
> stopping and restarding the service is usually enonght thought...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> On Machine A, the Network Utility says the tcp/ip default port is
> 1059 (must be some default, because I did not set it), and Hide
> Server is not checked.
it's not a default... Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack had to be modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
> Do you have suggestions about this?
>
WinXP sp2 or personal firewall?
the Windows XP sp2 integrated Firewall closes all ports... you have to add
an exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
please excuse my poor english... hope it's understandable
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
I am having the same problem, but I am using Enterprise Manager on the same
machine where the named instance is running. What can I do, please?!
TIA
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Sorry, I forgot to mention that I am using win2000p for dev and win2000
server for production
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
dl wrote:
> Hi Andrea
> I am having the same problem, but I am using Enterprise Manager on
> the same machine where the named instance is running. What can I do,
> please?!
> TIA
what kind of exception are you reported with?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your help. Your English is fine.
I don't know why, but it started working. I didn't change anything. But if
it's working, I won't complain.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hldmoFhkqsrU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> it's not a default... Microsoft only got 1 unique TCP/IP port for SQL
> Server assigned by IANA, port TCP/IP 1433... but named instances never
> listen to that port that is "reserved" for default instances... so
> Microsoft embedded an additional service in order to allow dynamic ports
> assignemen/resolution for named instance, and the MDAC stack had to be
> modified as well to integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
> instance for it's used port, and redirects all connections to that
> specific port, adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
> connection over a random tcp port greater than 1024 to destination port
> (say 1059). The Subscriber should be allowed to make inbound (ANY)
> connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
>
> WinXP sp2 or personal firewall?
> the Windows XP sp2 integrated Firewall closes all ports... you have to add
> an exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> please excuse my poor english... hope it's understandable
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
were reported.
The instance is listed in the computer's services, and it is running.
However, neither the computer name nor the new MSDE instance is listed in
the SQL Server Service Manager (although an instance on a networked computer
is listed). And I cannot connect via osql.
Any suggestions?
hi Paul,
Paul Pedersen wrote:
> I installed a named instance of MSDE SP4. It seemed to go OK, and no
> errors were reported.
> The instance is listed in the computer's services, and it is running.
> However, neither the computer name nor the new MSDE instance is
> listed in the SQL Server Service Manager (although an instance on a
> networked computer is listed). And I cannot connect via osql.
> Any suggestions?
if you can not connect from remote client, it can be depending on disabled
network protocols (default for MSDE installation, you can bypass at install
time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
time, using the Server Network Utility [svrnetcn.exe] to enable the
desired/required network protocol) or, for instance, firewall/network
problems (Windows XP sp2 Firewall requires to provide an exception for the
service or to the port)..
as you are reporting the SQL Server Service Manager does not list the
instances, I'd guess it's becouse the very first scenario
(http://support.microsoft.com/default...b;EN-US;814132)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||That did the trick. Thank you!
Is there some reason that disabling the protocols is the default? It seems
to me that without that, MSDE is completely unusable. Like I said before, I
couldn't even get osql to connect. Maybe that's a different problem.
One note: the Server Network Utility says that changes will take effect
after the service is restarted, but restarting MSDE didn't make it work. I
had to reboot the computer
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
> install time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later,
> at run time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> That did the trick. Thank you!
> Is there some reason that disabling the protocols is the default? It
> seems to me that without that, MSDE is completely unusable. Like I
> said before, I couldn't even get osql to connect. Maybe that's a
> different problem.
actually not... Microsoft provided a setup that should protect all "passive"
users from external malicious attacks (think of Slammer and the like) only
enabling trusted WinNT connections and disabling network protocols ...
and this is not a bad idea... always give the least required privilege
pattern :D:D
> One note: the Server Network Utility says that changes will take
> effect after the service is restarted, but restarting MSDE didn't
> make it work. I had to reboot the computer
stopping and restarding the service is usually enonght thought...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks again.
It took a fair amount of trial before I realized that to connect to a named
MSDE instance with osql, you have to preface the name with server\, even if
it's on the same machine.
Only one problem left. In testing, I uninstalled and reinstalled with
DISABLENETWORKPROTOCOLS=0. But the instance does not show up on the network.
In other words, I installed MSDE on Machine A. The Service Manager on
Machine A can see its own server, plus an instance of SQL Server on Machine
B. Machine B can see its own SQL Server instance, but cannot see the MSDE
instance on Machine A.
On Machine A, the Network Utility says the tcp/ip default port is 1059 (must
be some default, because I did not set it), and Hide Server is not checked.
Do you have suggestions about this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hk1c1Fhii6nU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> actually not... Microsoft provided a setup that should protect all
> "passive" users from external malicious attacks (think of Slammer and the
> like) only enabling trusted WinNT connections and disabling network
> protocols ...
> and this is not a bad idea... always give the least required privilege
> pattern :D:D
>
> stopping and restarding the service is usually enonght thought...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> On Machine A, the Network Utility says the tcp/ip default port is
> 1059 (must be some default, because I did not set it), and Hide
> Server is not checked.
it's not a default... Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack had to be modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
> Do you have suggestions about this?
>
WinXP sp2 or personal firewall?
the Windows XP sp2 integrated Firewall closes all ports... you have to add
an exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
please excuse my poor english... hope it's understandable
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
I am having the same problem, but I am using Enterprise Manager on the same
machine where the named instance is running. What can I do, please?!
TIA
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Sorry, I forgot to mention that I am using win2000p for dev and win2000
server for production
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
dl wrote:
> Hi Andrea
> I am having the same problem, but I am using Enterprise Manager on
> the same machine where the named instance is running. What can I do,
> please?!
> TIA
what kind of exception are you reported with?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your help. Your English is fine.
I don't know why, but it started working. I didn't change anything. But if
it's working, I won't complain.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hldmoFhkqsrU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> it's not a default... Microsoft only got 1 unique TCP/IP port for SQL
> Server assigned by IANA, port TCP/IP 1433... but named instances never
> listen to that port that is "reserved" for default instances... so
> Microsoft embedded an additional service in order to allow dynamic ports
> assignemen/resolution for named instance, and the MDAC stack had to be
> modified as well to integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
> instance for it's used port, and redirects all connections to that
> specific port, adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
> connection over a random tcp port greater than 1024 to destination port
> (say 1059). The Subscriber should be allowed to make inbound (ANY)
> connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
>
> WinXP sp2 or personal firewall?
> the Windows XP sp2 integrated Firewall closes all ports... you have to add
> an exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> please excuse my poor english... hope it's understandable
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Cannot connect to MSDE
Hello all,
I have two computers in LAN. Both computers are visible
one to another. First computer has MSDE installed on it.
Second cumputer runs application that needs to connect to
MSDE installed on the first computer. The problem is that
application installed on second computer cannot connect to
MSDE and i cant figure out why is that so.
The application running on first computer(the one that
has MSDE installed on it) can connect to MSDE without any
problems. MSDE is configured to use SQL Server
authentication. Can anyone help me please ?
Regards,
Tom
hi Tom,
Tom wrote:
> Hello all,
> I have two computers in LAN. Both computers are visible
> one to another. First computer has MSDE installed on it.
> Second cumputer runs application that needs to connect to
> MSDE installed on the first computer. The problem is that
> application installed on second computer cannot connect to
> MSDE and i cant figure out why is that so.
> The application running on first computer(the one that
> has MSDE installed on it) can connect to MSDE without any
> problems. MSDE is configured to use SQL Server
> authentication. Can anyone help me please ?
> Regards,
> Tom
MSDE installs by default disabling network protocols to prevent external
mailcius attacks...
you have to manually enable them, bot at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to setup.exe boostrap installer and/or later using the Server
Network Utility (svrnet.cn.exe) to enable the desired/required network
protocol (usually TCP/IP)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP
stations) and have all my tools installed on one station (MSDE, Visual
Studio, you great DbaMGR2k, Book Online, etc) and things are working
fine, but I can't access SQL from the other stations. All the stations
can see each others and share all other resources.
- I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was
- I tried added named pipes too but it doesn't help
- I logged in as Administrator but still have the problem
Questions:
- Do I need to install MSDE on all the stations?
- Could Windows XP SP2 firewall be the problem?
Thanks
Richard
Andrea Montanari wrote:
> hi Tom,
> Tom wrote:
>
> MSDE installs by default disabling network protocols to prevent external
> mailcius attacks...
> you have to manually enable them, bot at install time providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to setup.exe boostrap installer and/or later using the Server
> Network Utility (svrnet.cn.exe) to enable the desired/required network
> protocol (usually TCP/IP)
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> I'm having the same problem. I am working in a peer-to-peer LAN (all
> XP stations) and have all my tools installed on one station (MSDE,
> Visual Studio,
> you great DbaMGR2k
thank's :D
>, Book Online, etc) and things are
> working
> fine, but I can't access SQL from the other stations. All the
> stations can see each others and share all other resources.
> - I used svrnetcn.exe to make certain TCP/IP protocol was installed,
> it was
> - I tried added named pipes too but it doesn't help
> - I logged in as Administrator but still have the problem
> Questions:
> - Do I need to install MSDE on all the stations?
no, you don't
> - Could Windows XP SP2 firewall be the problem?
probably yes...
please have a look at http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
personally I always solved my troubles adding an exception to the firewall
for the related TCP/IP port both specifying a subnet range and/or defined
pc's IP ... if you can restrict the IP list your server will appreciate it
:D
for named instance the UDP 1434 port must be opened as well, if you do not
specify an ALIAS on all remote clients pointing to a static defined (and not
dinamically assigned) port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for the links
> probably yes...
> please have a look at http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
I tried what it said and I even tried disabling the XP SP2 firewall on
both PCs but the second PC (the one without MSDE installed) still can't
see the first PC (with MSDE and the databases).
I tried using your utility, DbaMGR2k, on the second PC but when I try to
connect, I get the error message, "429 - ActiveX component can't create
object"
I am new to MSDE and I am not sure if I need aliases, named pipes,
special libaries etc. What I do have configured is TCP/IP protocol and
I checked and it uses the default port 1433. I also only have one
instance, the default, created during installation.
I could try to install MSDE on a third PC with all the defaults and see
what happens, but I'm fairly certain I didn't change anything from the
recommended defaults during the initial installation.
Any ideas why the other stations still can't see MSDE?
Thanks.
Richard Fagen
> personally I always solved my troubles adding an exception to the firewall
> for the related TCP/IP port both specifying a subnet range and/or defined
> pc's IP ... if you can restrict the IP list your server will appreciate it
> :D
> for named instance the UDP 1434 port must be opened as well, if you do not
> specify an ALIAS on all remote clients pointing to a static defined (and not
> dinamically assigned) port
|||hi Richard,
Richard Fagen wrote:
> I tried what it said and I even tried disabling the XP SP2 firewall on
> both PCs but the second PC (the one without MSDE installed) still
> can't see the first PC (with MSDE and the databases).
can you reach the MSDE installed pc from the remote client for standard
sharing?
can you ping it?
can you telnet it, in the form
c:\..\>telnet ComputerName 1433;
if the screen becomes black you are in... then just type QUIT to exit..
> I tried using your utility, DbaMGR2k, on the second PC but when I try
> to connect, I get the error message, "429 - ActiveX component can't
> create object"
DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of
the presence several international localizations and service pack level..
in the application folder you can find the Depend2k.txt file which lists, in
the SQL-DMO section, all the required files you can get from the MSDE
installed pc and copy on the destination pc.. please fullfill the indicated
hyerarchy and register via regsvr32 the required file (just 1)
please feel free to privately contact me for any question or concern about
the project, as long as for suggestions and feedback, as this is OT in this
public newsgroup...
> I am new to MSDE and I am not sure if I need aliases, named pipes,
> special libaries etc. What I do have configured is TCP/IP protocol
> and I checked and it uses the default port 1433. I also only have one
> instance, the default, created during installation.
that's ok.. the default instance listens on TCP/IP 1433 (if it has not been
changed) and does not require an ALIAS nor the UDP 1434 port for the SQL
Server Resolution Service to work as it is not needed..
> Any ideas why the other stations still can't see MSDE?
if all TCP/IP requirements and checks has been satisfied, I do think it's
just a network problem.. please verify your connectivity other then SQL
Server...
again... for my personal tests I just referenced
http://support.microsoft.com/default.aspx?kbid=841252 and worked like a
charm...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I have two computers in LAN. Both computers are visible
one to another. First computer has MSDE installed on it.
Second cumputer runs application that needs to connect to
MSDE installed on the first computer. The problem is that
application installed on second computer cannot connect to
MSDE and i cant figure out why is that so.
The application running on first computer(the one that
has MSDE installed on it) can connect to MSDE without any
problems. MSDE is configured to use SQL Server
authentication. Can anyone help me please ?
Regards,
Tom
hi Tom,
Tom wrote:
> Hello all,
> I have two computers in LAN. Both computers are visible
> one to another. First computer has MSDE installed on it.
> Second cumputer runs application that needs to connect to
> MSDE installed on the first computer. The problem is that
> application installed on second computer cannot connect to
> MSDE and i cant figure out why is that so.
> The application running on first computer(the one that
> has MSDE installed on it) can connect to MSDE without any
> problems. MSDE is configured to use SQL Server
> authentication. Can anyone help me please ?
> Regards,
> Tom
MSDE installs by default disabling network protocols to prevent external
mailcius attacks...
you have to manually enable them, bot at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to setup.exe boostrap installer and/or later using the Server
Network Utility (svrnet.cn.exe) to enable the desired/required network
protocol (usually TCP/IP)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP
stations) and have all my tools installed on one station (MSDE, Visual
Studio, you great DbaMGR2k, Book Online, etc) and things are working
fine, but I can't access SQL from the other stations. All the stations
can see each others and share all other resources.
- I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was
- I tried added named pipes too but it doesn't help
- I logged in as Administrator but still have the problem
Questions:
- Do I need to install MSDE on all the stations?
- Could Windows XP SP2 firewall be the problem?
Thanks
Richard
Andrea Montanari wrote:
> hi Tom,
> Tom wrote:
>
> MSDE installs by default disabling network protocols to prevent external
> mailcius attacks...
> you have to manually enable them, bot at install time providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to setup.exe boostrap installer and/or later using the Server
> Network Utility (svrnet.cn.exe) to enable the desired/required network
> protocol (usually TCP/IP)
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> I'm having the same problem. I am working in a peer-to-peer LAN (all
> XP stations) and have all my tools installed on one station (MSDE,
> Visual Studio,
> you great DbaMGR2k
thank's :D
>, Book Online, etc) and things are
> working
> fine, but I can't access SQL from the other stations. All the
> stations can see each others and share all other resources.
> - I used svrnetcn.exe to make certain TCP/IP protocol was installed,
> it was
> - I tried added named pipes too but it doesn't help
> - I logged in as Administrator but still have the problem
> Questions:
> - Do I need to install MSDE on all the stations?
no, you don't
> - Could Windows XP SP2 firewall be the problem?
probably yes...
please have a look at http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
personally I always solved my troubles adding an exception to the firewall
for the related TCP/IP port both specifying a subnet range and/or defined
pc's IP ... if you can restrict the IP list your server will appreciate it
:D
for named instance the UDP 1434 port must be opened as well, if you do not
specify an ALIAS on all remote clients pointing to a static defined (and not
dinamically assigned) port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for the links
> probably yes...
> please have a look at http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
I tried what it said and I even tried disabling the XP SP2 firewall on
both PCs but the second PC (the one without MSDE installed) still can't
see the first PC (with MSDE and the databases).
I tried using your utility, DbaMGR2k, on the second PC but when I try to
connect, I get the error message, "429 - ActiveX component can't create
object"
I am new to MSDE and I am not sure if I need aliases, named pipes,
special libaries etc. What I do have configured is TCP/IP protocol and
I checked and it uses the default port 1433. I also only have one
instance, the default, created during installation.
I could try to install MSDE on a third PC with all the defaults and see
what happens, but I'm fairly certain I didn't change anything from the
recommended defaults during the initial installation.
Any ideas why the other stations still can't see MSDE?
Thanks.
Richard Fagen
> personally I always solved my troubles adding an exception to the firewall
> for the related TCP/IP port both specifying a subnet range and/or defined
> pc's IP ... if you can restrict the IP list your server will appreciate it
> :D
> for named instance the UDP 1434 port must be opened as well, if you do not
> specify an ALIAS on all remote clients pointing to a static defined (and not
> dinamically assigned) port
|||hi Richard,
Richard Fagen wrote:
> I tried what it said and I even tried disabling the XP SP2 firewall on
> both PCs but the second PC (the one without MSDE installed) still
> can't see the first PC (with MSDE and the databases).
can you reach the MSDE installed pc from the remote client for standard
sharing?
can you ping it?
can you telnet it, in the form
c:\..\>telnet ComputerName 1433;
if the screen becomes black you are in... then just type QUIT to exit..
> I tried using your utility, DbaMGR2k, on the second PC but when I try
> to connect, I get the error message, "429 - ActiveX component can't
> create object"
DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of
the presence several international localizations and service pack level..
in the application folder you can find the Depend2k.txt file which lists, in
the SQL-DMO section, all the required files you can get from the MSDE
installed pc and copy on the destination pc.. please fullfill the indicated
hyerarchy and register via regsvr32 the required file (just 1)
please feel free to privately contact me for any question or concern about
the project, as long as for suggestions and feedback, as this is OT in this
public newsgroup...
> I am new to MSDE and I am not sure if I need aliases, named pipes,
> special libaries etc. What I do have configured is TCP/IP protocol
> and I checked and it uses the default port 1433. I also only have one
> instance, the default, created during installation.
that's ok.. the default instance listens on TCP/IP 1433 (if it has not been
changed) and does not require an ALIAS nor the UDP 1434 port for the SQL
Server Resolution Service to work as it is not needed..
> Any ideas why the other stations still can't see MSDE?
if all TCP/IP requirements and checks has been satisfied, I do think it's
just a network problem.. please verify your connectivity other then SQL
Server...
again... for my personal tests I just referenced
http://support.microsoft.com/default.aspx?kbid=841252 and worked like a
charm...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Sunday, February 12, 2012
Cannot Connect to an MS SQL Server
Hi,
I've developed an application that connects to an MS SQL server to read and write from a database. I have tested the program on about 6 computers (all on different networks and internet connections, etc...) and they can all access the database remotely just fine.
However, today I tried it on another PC (i.e. the 7th computer) and for some reason it won't connect. This computer is definitely on the internet as I can surf the web with it just fine, but every time I try to run the program it comes up and says that it cannot connect to the database. I can't remember the exact error message, but it was behaving as if the computer wasn't on the internet. What might cause a problem like this?
I did notice that this PC is running Norton Antivirus. All the other computers I tested on were not using Norton. Could Norton be the possible cause (i.e. might it be blocking a port or something like that). I will test it without Norton running, but I just thought I'd ask here too to see if anyone knows other possible reasons why this would be happening.
Thanks.
Have you tried to ping the IP/DNS name of the SQL Server machine?|||moving to SQL Server Data Access forum.|||Yes. Norton Antivirus could be the cause of the issue. Try run your app with Norton disabled. I assume all your 7 machines are clients and the SQL Server is always the one.
One more thing you can check is to see if you have outdated alias defined on the 7-th machine. Use c:\windows\system32\cliconfg.exe or SQL Server Configuration Manager (if you app use sqlncli.dll) to check it.
Subscribe to:
Posts (Atom)