Sunday, March 25, 2012
Can't Find SQL Native Client in ODBC Connection Manager
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing th
e
>SQL Native Client to not show up in the list of available ODBC data sources?[/vbcol
]
Can't Find SQL Native Client in ODBC Connection Manager
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing the
>SQL Native Client to not show up in the list of available ODBC data sources?
Can't find server
I installed the old MSDE 2000 (not release a) on a Windows XP Pro machine. I
manage the DB with the MSDE Manager from Vale Software. On the machine it
self, it works fine. I can select the DB and connect as 'sa' with password.
But on every other machine in the network, I can't connect to the DB. I can
ping to the server, that's no problem. I can chose the server in MSDE
Manager (and other DB-Tools like 'Aqua Data Studio' and 'DBVisualizer') but
I always get an error message like 'Cannot find server'. On the XP machine
there is no firewall running and -of course- the SQL-Server task is started.
The port 1433 isn't blocked.
Have enyone an idea why I can connect the DB on the machine it self but not
from every other machine in the network?
Thanks a lot
Dani
It's possible that the server does not have the network connectivity library
enabled.
i don't know how re-enable it in MSDE after MSDE is already installed.
Although i know it can be done, i read it a few days ago in the MSDE2000A
readme.
If it were SQL server, i'd say use the "Server Network Utility" (i think
it's called that). In that you can enable/disable tcpip,netbios,
multiprotocol, flatulance, etc.
"Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
news:2lk43sFd4pjhU1@.uni-berlin.de...
> Hello
> I installed the old MSDE 2000 (not release a) on a Windows XP Pro machine.
I
> manage the DB with the MSDE Manager from Vale Software. On the machine it
> self, it works fine. I can select the DB and connect as 'sa' with
password.
> But on every other machine in the network, I can't connect to the DB. I
can
> ping to the server, that's no problem. I can chose the server in MSDE
> Manager (and other DB-Tools like 'Aqua Data Studio' and 'DBVisualizer')
but
> I always get an error message like 'Cannot find server'. On the XP machine
> there is no firewall running and -of course- the SQL-Server task is
started.
> The port 1433 isn't blocked.
> Have enyone an idea why I can connect the DB on the machine it self but
not
> from every other machine in the network?
> Thanks a lot
> Dani
>
|||If you run svrnetcn.exe from the /Program Files/Microsoft SQL
Server/80/Tools/BINN folder it will bring up the Server network utility, you
can make sure the network libraries are enabled.
HTH
Dylan Kruger
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:eGyjL5ZaEHA.1048@.tk2msftngp13.phx.gbl...
> It's possible that the server does not have the network connectivity
> library
> enabled.
> i don't know how re-enable it in MSDE after MSDE is already installed.
> Although i know it can be done, i read it a few days ago in the MSDE2000A
> readme.
> If it were SQL server, i'd say use the "Server Network Utility" (i think
> it's called that). In that you can enable/disable tcpip,netbios,
> multiprotocol, flatulance, etc.
>
> "Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
> news:2lk43sFd4pjhU1@.uni-berlin.de...
> I
> password.
> can
> but
> started.
> not
>
|||Yeah, exactly that's it! The TCP/IP was disabled. I don't now why but after
I startet again, it works fine.
1000 thanks to you...
Dani
1000 thanks
"Dylan kruger" <carmellobear1@.hotmail.com> schrieb im Newsbeitrag
news:eC7EjuaaEHA.3112@.tk2msftngp13.phx.gbl...
> If you run svrnetcn.exe from the /Program Files/Microsoft SQL
> Server/80/Tools/BINN folder it will bring up the Server network utility,
you[vbcol=seagreen]
> can make sure the network libraries are enabled.
> HTH
> Dylan Kruger
> "Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
> news:eGyjL5ZaEHA.1048@.tk2msftngp13.phx.gbl...
MSDE2000A[vbcol=seagreen]
it
>
|||It's a new feature of MSDE, that by default it doesn't act like any other
server application on earth.
Go figure.
Probably Microsoft's tired of hearing people XXXXX about being
wormed/hacked/infected, and they just say, "Fine, your XXX get's no
connectivity anymore. Suck it!"
"Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
news:2lmm2oFept7kU1@.uni-berlin.de...
> Yeah, exactly that's it! The TCP/IP was disabled. I don't now why but
after[vbcol=seagreen]
> I startet again, it works fine.
> 1000 thanks to you...
> Dani
>
> 1000 thanks
> "Dylan kruger" <carmellobear1@.hotmail.com> schrieb im Newsbeitrag
> news:eC7EjuaaEHA.3112@.tk2msftngp13.phx.gbl...
> you
> MSDE2000A
think[vbcol=seagreen]
machine[vbcol=seagreen]
> it
I[vbcol=seagreen]
'DBVisualizer')[vbcol=seagreen]
but
>
|||I had a similar problem - I was not able to connect to the MSDE from
any other machine. I had tried openning the TCP/IP Port (1433) and even
shutting down the Firewall.
Eventually, I was able to able to fix the issue by adding the registry
value for "ProtocolList" under HKEY_LOCAL_MACHINE -> SOFTWARE ->
Microsoft -> MSSQLServer -> SuperSocketNetLib
But now I have a different issue. How can I connect to the MSDE
instance with DBVisualizer? I tried to create a connection but when I
try to select / edit a Driver the drop down is empty and I cannot get
one from the list that I get by hitting the Edit button.
Please help.
- manzoor
Monday, March 19, 2012
Can't Deploy AdventureWorks Database
Hi All,
I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.
For some reason, I encountered the following error (after deployment during processing):
Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0
Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.
Nothing seems to work. Any help would be greatly appreciated!
Thanks,
Raj
Hi,
We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:
Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0
This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.
Brad
|||We are having the exact same error. Did you all find a solution?
|||I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.
G'luck.
|||Hi everyone!I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||
Try:
Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.
Can't Deploy AdventureWorks Database
Hi All,
I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.
For some reason, I encountered the following error (after deployment during processing):
Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0
Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.
Nothing seems to work. Any help would be greatly appreciated!
Thanks,
Raj
Hi,
We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:
Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0
This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.
Brad
|||We are having the exact same error. Did you all find a solution?
|||I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.
G'luck.
|||Hi everyone!I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||
Try:
Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.
Sunday, March 11, 2012
Can't Deploy AdventureWorks Database
Hi All,
I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.
For some reason, I encountered the following error (after deployment during processing):
Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0
Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.
Nothing seems to work. Any help would be greatly appreciated!
Thanks,
Raj
Hi,
We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:
Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0
This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.
Brad
|||We are having the exact same error. Did you all find a solution?
|||I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.
G'luck.
|||Hi everyone!I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||
Try:
Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.
Thursday, March 8, 2012
can't debug SP in VS 2003
My config:
* Windows XP Pro
* VS.NET 2003
* SQL Server 2000 SP3a
* Breakpoints are not hit in stored procs either... they become question
marks when I run and the tooltip text says "The breakpoint will not
currently be hit. Unable to bind SQL breakpoint at this time. Object
containing the breakpoint not loaded."
I have followed ALL these instructions :
* I have granted myself EXEC permissions on sp_sdidebug -- GRANT EXEC
on master..sp_sdidebug to [MYDOMAIN\ME]
* I have run -- exec sp_sdidebug 'legacy on'
* Sqlle.dll and sqldbreg2.exe exist on your debugging workstation. The
former library is the SQL language engine for the debugger.
* Sqldbg.dll exists on both the database server and the debugging
work-station. This library is the SQL debugging proxy.
* Mssdi98.dll exists in the \binn subfolder of every SQL Server instance
on the database server.
* If you're running the full version of SQL Server
* My domain account has permission to the master database itself.
* I re- execute sp_sdidebug 'legacy on' every time I reboot SQL Server.
* I turned on SQL debugging for every project in my VS solution -
* Connection pooling is disabled.
Any help?i usually debug sp's using query analyzer. i right click the stored
procedure in the debug manager and chose debug. u can even pass paramaters
to it
"Oleg Bulay" wrote:
> I can't debug SP in VS 2003
> My config:
> * Windows XP Pro
> * VS.NET 2003
> * SQL Server 2000 SP3a
> * Breakpoints are not hit in stored procs either... they become question
> marks when I run and the tooltip text says "The breakpoint will not
> currently be hit. Unable to bind SQL breakpoint at this time. Object
> containing the breakpoint not loaded."
> I have followed ALL these instructions :
> * I have granted myself EXEC permissions on sp_sdidebug -- GRANT EXEC
> on master..sp_sdidebug to [MYDOMAIN\ME]
> * I have run -- exec sp_sdidebug 'legacy on'
> * Sqlle.dll and sqldbreg2.exe exist on your debugging workstation. The
> former library is the SQL language engine for the debugger.
> * Sqldbg.dll exists on both the database server and the debugging
> work-station. This library is the SQL debugging proxy.
> * Mssdi98.dll exists in the \binn subfolder of every SQL Server instance
> on the database server.
> * If you're running the full version of SQL Server
> * My domain account has permission to the master database itself.
> * I re- execute sp_sdidebug 'legacy on' every time I reboot SQL Server.
> * I turned on SQL debugging for every project in my VS solution -
> * Connection pooling is disabled.
> Any help?
>
>|||Check out this article...
http://support.microsoft.com/?kbid=839280
HTH
"Oleg Bulay" wrote:
> I can't debug SP in VS 2003
> My config:
> * Windows XP Pro
> * VS.NET 2003
> * SQL Server 2000 SP3a
> * Breakpoints are not hit in stored procs either... they become question
> marks when I run and the tooltip text says "The breakpoint will not
> currently be hit. Unable to bind SQL breakpoint at this time. Object
> containing the breakpoint not loaded."
> I have followed ALL these instructions :
> * I have granted myself EXEC permissions on sp_sdidebug -- GRANT EXEC
> on master..sp_sdidebug to [MYDOMAIN\ME]
> * I have run -- exec sp_sdidebug 'legacy on'
> * Sqlle.dll and sqldbreg2.exe exist on your debugging workstation. The
> former library is the SQL language engine for the debugger.
> * Sqldbg.dll exists on both the database server and the debugging
> work-station. This library is the SQL debugging proxy.
> * Mssdi98.dll exists in the \binn subfolder of every SQL Server instance
> on the database server.
> * If you're running the full version of SQL Server
> * My domain account has permission to the master database itself.
> * I re- execute sp_sdidebug 'legacy on' every time I reboot SQL Server.
> * I turned on SQL debugging for every project in my VS solution -
> * Connection pooling is disabled.
> Any help?
>
>
Wednesday, March 7, 2012
Cant create index on view
SQL Server 2005 (SP2) Developer edition on XP Pro
Can anyone help with setting up an indexed view? Part of the select statement calls a couple of very simple functions which are deterministic. The functions which are shown below do not perform any aggregation.
This is the error message.
Msg 8668, Level 16, State 0, Line 2
Cannot create the clustered index 'IX3_SA' on view 'XPS.dbo.SA_INDEXED' because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from select list.
Function definitions:
create FUNCTION [dbo].[MonthName](@.MonthNo TINYINT)
RETURNS CHAR(3)
with schemabinding
AS
BEGIN
DECLARE @.MonthName CHAR(3)
IF @.MonthNo BETWEEN 1 AND 12 SET @.MonthName = SUBSTRING('JanFebMarAprMayJunJulAugSepOctNovDec',((@.MonthNo*3) -2),3)
RETURN ISNULL(@.MonthName,'')
END
create FUNCTION [dbo].[FinancialYear](
@.Year INT,
@.MonthNo TINYINT,
@.YearEndMonthNo TINYINT)
RETURNS INT
with schemabinding
AS
BEGIN
DECLARE @.FinancialYear INT
IF @.MonthNo <= @.YearEndMonthNo
SET @.FinancialYear = @.Year
ELSE
SET @.FinancialYear = @.Year + 1
RETURN @.FinancialYear
END
The first part of the select statement is as follows:
(SELECT
count_big(*) as CB,
dbo.FinancialYear(YR.Number,MTH.Number,YEAR_END_MONTH) AS REPORT_FINANCIAL_YEAR,
dbo.MonthName(MTH.Number) + ' ' + CAST(YR.Number AS CHAR(4)) AS REPORT_MONTH,
dbo.MonthName(YEAR_END_MONTH) + ' ' + CAST(dbo.FinancialYear(YR.Number,MTH.Number,YEAR_END_MONTH) AS CHAR(4)) AS REPORT_FINANCIAL_YEAR_END,
I can create the index on this view if I comment out the calls to the functions so I know that is where the problem is. I can't however see why this is erroring as both only return a single value without any agregation.
Anyone got any ideas on this?
Thanks in advance
David.
Well that met with a deafening silence.
The answer was to move these function calls out of the indexed view definition into a standard view that sits above it.
Saturday, February 25, 2012
cant connecto to sql server 2000 sp3a in windows server 2003
and win 2000 pro, before i had the sql server 2000 on a windows 2000 server
and all worked fine, but two days ago i changed to windows server 2003
standard and the problems began...
when i try to connect to sql by odbc or by another way its the screen that
appears, the extrange is that in downstair there are 4 pcs and that 4 can
connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
english and just 1 XP in spanish can connect the other 2 not, i thought it
was a problem with the server but now i connect a new laptop with winXP
spanish SP2 and it works fine... so i dont know what to do, all pcs have
mdac 2.8
now i thought its problem with clients but i cant find difference between
pcs except for the language
what can be?
i tried to connect by IP, i checked the port and nothing works =(
begin 666 error.gif
M1TE&.#EA!P+&`.8``````.5($P!+YP`DI@.`.?7BH]%MDJ_'OXK$M"B)T]>OH
MUV-OA@.!BZ0`[X =$P7%O9)FWU.A^929#<2\\(,KH_P!F_P!:YP`?TK;8\0@.A
MDC.9_^?U_XVJQ !0WCA2L !F_^_8TN9J38V5GA9J[L/%O]5*)0!;\ !3YJ;-
M\WF:O `FK ``2 H8@.QHO6/___^5>-TZ&W^R1>4.$[4)6=]4U!"&)_P!*W-[H
M\["TM,O<^0!9^)RBS-K9S!,D3%2/\0=R_7"*M.[O]HJ;T 4VM@.!,[QM0OCI%
MF_"FE)B[]KO(Z0)D]1DFB@.@.QV*W"V4ANM@.A5W0`SF:>LKH"HV@.%(T0`[TJRH
MF=]3,$-CF^;HZP!S_2N0__'Y_YB=I-W?[0!1\-?L_VB"S*TY'+W W2DZF7)^
MDP`@.R-[O_P!#W'N:R-5%&YNJV1J"_X>T^^9E0RL_8KC<_P`SS D<BN50(N=S
M63^7_P!@.[EEUQ@.!#S]?>W4I5HP`>H `3C&:9__.[K;/!S/___R'Y! 44`'\`
M+ `````'`L8```?_@.!."@.E.%-H>''1T6C!8,#(V1DI.4E9:7F)F:FYR=GI8F
MH:*CI*6FIZBIJJNLK:ZOKY^RL[2UMK><7EXG)P*^O\#!5 K$Q(.%2C]KRVM:
MSG30T=+3U-76U]C9VMO<W=[?X.'BX^3EYN?HZ>KK[.?.[UHU-6L_5'#%A!9*
MR<QK\O!:- @.$2+"@.P8,($RI<R+"APX<0(TJ<2+&BQ8L8,VK<R+&AO(\@.0_;K
M]^.'B6$*)MQ1]*AELI)98LJ<&;/D#YHX<^K<R;.GSY] @.PH=2K2HT:-(DRH%
M6J&ITZ=0HTJ=2K6JU:M8LVK=NG7GOJ\ZPH:M0[9L'5XG0IVXT R#EG3N2_USN
MLTFWY->[>//JW<NWK]^_@. ,+'DRXL.'#B!,K7LRXL>/'D"/C;0DI$EJTBA0A
M0G0'CAX%<&Q,R=R(\J.[ILO"6LVZM>O7L%GAFDV[MNW;N'/KWBW+AQD7P(,+
M'^X"S%LXR/4@.?ZNHM.GGE'E+GTZ]NO7KV+-KWR[KLG<?"F)$F!.BC?D7Z%]8
M66\EC1408)"K4*%G`!SFBQA!-TW)N___``8HX( $%FC@.@.0@.FJ.""##;HX(,0
M&IC9A!16:.&%&&:HX88<=NCAAR!JZ$(,1Y0H7@.0HCC<'>>594 4()-\@.W``'*
MW=><?OL]TE^$//;HXX] !BGDD$0&&.*12":IY/^23';H0@.0E'A'#B2FJ6-X+
M)83A@.HPT(G>(<SGJ*$F19)9IYIEHIGEFDVRVZ>:;;+HPAXDGK LAB>6VHE^66
M<)0QHW)4V'#C?I>H:>BAB":JZ**,-HKHA2Z$,&4,(,A)WGDON-#'>GO:4X8*
M!)0!1Z =G, (!@.FTE `&+>60PR1 8N!"#@.(BL8$+** U`@.K H3 "+\#5>FNN
M9@.:[H*N.)JOLLLPVBU8P`D0:@.7C!A7!EIL!QJJ6G,Y9!Q1EGH &6!"T(\\0@.;
M+D#QB*L9P-HC$BYXP$(&;'SAGZQ%&!%$$[QLD,,`2^ 1Q!,G`,<"@./CJRV^9
M!A^;0P;.1BSQQ!3["*W_"VU4&5R>V+H@.AQPN;GO!IZ%^&RXO) KC0Q1"/_,9"
M2QED0-:8/!H\1<$N0'R9P:+%,0"Z>4 L@.PL[=-#P?SQ/X3/#+AR\8,P51RWU
MU%0_&PS&*:X87,<?]SIR*!Z>T9^%B0`W!AUF.V"$74$1U8!7[CPA0R,`(>$
MO2? ZP(2O,B0@.]R_YFTWL,'A;"Q:<>]P6=PLW %L%RH<[5_BWNG--^%WG_#W
MKR/,*OC>:-F-=^A-5SXX+[+Z6X#AP*)P*P:!5RW[[+2K"8P++]BY8@.C#=>WU
MME1<$#85OS R=!="6,#L_T7;3!;@.@.109-`#'%N"X8X 2]+MB1![D6W#H&
M_QY =("N]^!CSP(+ZK/?B Q!N' #W>HW`EP&!E<"O_STPPO&]VJH6_:VYP-R
MF2][:B@..``6HO7;9KVF1.-_WDB<K#QC!!6(80OV DR\7)(%L-*N="$=(0@./I
MXH3 >D$(=&>MX%C!=W+84P,
M`$8TV%MNU3@.7!&$(<3/""3+@.`";>P8E);%HH#%:*)X@.!.#!(F1:WV#0NGL*+
M8#0!$QV 13$V[@.XF",(3-Q $%L2/!6Q\HAO?,@.HSAL**6.09< ;@.1C<:S06$
MC(TB%\G(1CKRD9",I"09><)*>L$%5EBAG7@.G'!BF`?\!+IAA# 2\P0Y29('IC
MR)X+4@.D$!PRQC$T+BRC,R$7@.Q"$!7<!5`@.IIRT+ZLA0)#,(=X K:$4'2N"RSP
MXRF"><7AQ.&7T=L!$.- G&<JDXPLZ*,6;1E%L^$AF[7<YA@.G2<YRFO.<Z$RG
M.EMA24RVP5HM!$X;@.M.U`'PRE#-4P1Y(V8"TA.(-36/>#9(I!E<:C(EX,=@.^
M$.I$%BCA!'9PX@.D86L=7.M2B?+$EN@.P0B@.+N`']-^XLMF;B^]6%T'YT#SA*J
MV+22.E2A"0WI5RC*`K6Y``-CR !&%0K3O(CEIT -JE"'2M2B&O6H2$VJ4I?*
MU*8Z]:E0C:I4IXK4$WKL!>__Y"3&\D3/`'@.5E#-L@.#Y)Z8NR`)0%Z!("_L0`
MA1\8+'I 4 (*V+ /F&Z4#^2*PQOHZL0XW#6O)T7H79"0`R68;0<.#4(7IC""
M+P1A"4/H*5X(:UBBL0"N...@.`74^Z#W@.A]I1 S.QF)5M7F>[CKT*(P]^,L+X!
MG&"G(26M9&9+V]K:]K:XS:UDB.J"-&!UGO+D6,>\2@.-0^J(!<-AG`P1@.@.;(8
MS&QC8&.ZW-JT"D@.AEU\HPA XFT#IL6 (!9S5&.*@.A.Y*X;LG#2]>$I $%V@.6
MO0GXXMGB\#SAK+>][]VN%.)W@.S%L5[):6-MVE;!?^?F7LU\ASC[,^UU>!><+
M/H#M_TM-J]L*6QBW7,FPAC?,X0Y[F"L_[:T5L-J'K0I7#IHB+BB)0 3D*E<`
MHMC'^G[ @.)?]8,8W9D%)')"!>=6A*>M[RA#6YX"F3&%],FO*D/'HE" ;V<E.
MJ<,`6!"'(C=%RDL(`A!^7 &70OG*4ZZR4QP0!Q\#F050L0#[QESF)'<9S5'Q
M,IR77.0$V&%]J0S"%-Y\YCY_^,^ #K2@.!TWH0AOZT(<.2V]!EIY&OZ">*G8!
MBUU,5A/@.I2Z8ODE-;(+H#(] FB[H-*+?L($$5 "O>(B#J%...ZE:[^M6PCO56
M7$"#-)2 /;C^F%>)6UQ)MSBYE;YTINLBDV$;^]C(3C:FE?^P9&4[^]G01K8:
MXF<&),PKVB61M;:WS>UN>QO19BA!&L;]HG*/>]PT2'>ZM31I8"\W%'DY=K&S
M_>UZ_YG9;1Z"O?...[W[[^]]1X0,(PH" @.AO\X @./`PCXT.X7ER+>] :XQ"=.
M\8I;_.*O!DM8\$J<C@./'#'S0A0`HO5P!F*H19-'+5"[,\I8S!N,PY[#+9T[S
MP!BUDC^U)(MWOG.2-\ &5'C+6S:3B Q!Z^A(3[K2E\[TICO]Z5"/NM2G3O6J
M6_WJ6*\ZN+;.]:Y[_>M@.#[O8QT[VLIO][&A/^QD$(/:PAE7L5(C[#-W]<Z';
M_>YXS[O>]\[WOOO][X /O. '3_C_PAO^\(A/O.(7S_C&._[QD(\\X>>^!R:,
MX G%R+SF-\_YSGO^\Z /O>A'3_K2F_[TJ$^]ZE?/^M:[_O6PC[WL9T_[U#=@.
M`)6_?.UWS_O>^_[WP ^^\(=/_.(;'_6WSSWFC\_\YCO_^="/OO2G3WW3)]_R
MRZ^^]K?/_>Y[__O@.+_[U=1_^\IO__.A/O_JA/_[LK__]\(^__.<__P;H0?GT
MS[_^]\___A/?_OCG?P(X@. 18@. :H>0"(?0>X@. S8@. X8?@.E(?@.\X@.118@.1;H
M>Q'H?A>X@.1S8@.1[H>1FH>GC0!5A0@.B98@.B3 `Q^X@.BS8@.N 7@.J9'`@.(C1Q[G
M`EN `RKH_X(ZN(,\*'[WIX"EAP7 L07"X0<X0(1#2(0W.( ```">YX2?!X4]
M.(542'LP*'IX@. 4T*!PSL (KT -(F(081 *OUX1-.'M2*(6BIX::YX1LN'EO
M6(5R.(>G=X6@.EX58$(; @.0<KP )[L ) ,!Q;$ 1;D ,XT'IQ"'N)&'J+2 R-
MJ "/2(>2.(F99X>>AP=9]B> ,K``4P``4)M 6B.(0WL 5-<(BJ%X=FZ(BK
M"(FMZ(II>(:K"(6M
M4 0P``8VN 4;$(W L0$WL $I0(:I]X9IN(NZN(W>F'G?^(O;V/^+G.>&W4B.
MXQB)PKB.+DB,FX>)S/.,R:B'TQB-]DB$-W #.4 &.7AZVHB.`"F.OJB&X7B.
MOTB.O3B+W3B0",F.#CF'[IAYF-@.%MS*/HR@.<]AB-9K"19B"*.6 &"\ %V0B'
M`6F0)GF0*&F.XMB0W/B-*MF0ZOB0,MF!$5D,8H 'I0B-&;D%0" !/BD!*Y "
M6\"11+D%7Y #3; `_6AZMUB2+_F4W-B24CF.*0F04)F.,YF5[?B#$MAY?H"3
M.KF3J44`<1 '!""4'/D%:OD%&W"42> &J(AZOLB+4XF0KXB+NUB++$F0"DF+
MN0B+M*B5@.OF!-4D,?B &U:B11;D%.07_!7N !D.YEI))`4F0!"T@.`H.9F9J9
M?H6I`(=9C419E%<0!U# `I IF9*9`Y5YF9O9FJ[9?9UYF!])E)*Y!:-9FFC0
MEA2PF[Q)`:IIF9CYFL(YG,\7FWXPFZBIEAMPFZ:Y`;W9FZK9! *Q)G-19G<+7
MF1#@.!TF0G&NYG*39G,_)FTG0!! PG>H7DTQIG>I9?URI@.9OG!_"9`VH9GF;
MG+D9GA2 `4W0!%=@.GDQYEW]YBPK9>>B9EW\9E0`:BX&YG@.RZ?IW)`TW@.!TT@.
MG_1IGV; FV^0H6^ `N0I`7 IER1YD 39AD]8>E#IBC!9ERO9H"QZ?IVI`!P`
MGTF0`^&YG'L`_P4$``3.J:$9B@.(0``$&T -*":+@.2*(C"HZYB(M^295%6I55
M69 %VJ)26ISM&7H\D (<``$S^IPX!05>.@.880 $\ZJ,0D (]X 8BF8U):J1M
MN*8D294+2J).JJ(F&:53>J?&]Z(*@. ,<D*5-$*84\ 5H0"-%4*A%``52(*8;
M^J-H( $MP(^(&)4G6:1\*8L)^8KEF*)/ZI1XVJG;IZ<*P 58ZJ<8D*%(L*$H
M@. *HB@.%D6J82(*38R'HON
M^J/"Z@.0](*1Q*:M.FHB[&JTHV:12N:FT:J>]FJU66*6D%P4+$*S"VO^G$)"J
M9-JG/7FF9-"L<HFI">J&`,J*2;JD+(FD"GJI]@.JOVIJOS/>KQ$ "9# #,T &
M*3"P6)JJ4@.`$5_"J+3 #(A"KM(>M^AJQ$\BOQ, #.$ &"S #;B !P8H$*" %
M+7"F"]"P2UE[!RJQ*$N8W'IZ/-"R) "P/_JQ+; `.."P*7NSPDFQG$<";@.`$
MXRH%
MKE>I]\J*37NS3\MY/$ &5["TL?>/(IJINZ>U6VNK=AFV.#NVG1<%Z8J&<EJ2
MU'JOYIB.:WJD5FF@.@.1FG>SNOLRJW$DNWPZ?_EY1*H&ZZD-8*N?3JEV [E;<Z
MK2C:I%R+N-JJN,5WN(?[I@.P9D+88NDTYIZ$;HGD+IYRKKYY+?*"+M6RZMRIY
MNH7+NK1:HB$*N&[;NCF[LN$7IX2;J06)NEAKNZP+N-1:O-7JN[WZNK_'M>TZ
MN7R;MW2IC:.+H(][O $:KTKJO)T+O.G7N^!;OM0'O<UWLN:[OBXJONS[OD[K
MOO [OX*)OKV'J;QWLK.HOE.XO^2+B/R[?__KC\W+?_:;OPF9P -<P),ZO?!:
MJ0+:O9?[P&B(OY@.[>D_IP $*F.XZH/@.JO5F+MQ?\A &<GB%<M<L[K_EWP&V;
MP)6KB(:+H'&[MC2L_[J:JHH(/,(@.BKO>R+QS6L-8V<(F++M#O,!L:[S]Q\(F
M&[BU:ZGRBJ_7*XL;?*NS>I6Z&\,XW*:#6ZUZJ;Q]6Z=0;,73:L5;K+JGF[SE
MZ+U+6J\?;*E1O+T+*<$4G,)PJ,9S?+7^*ZD3+']*_+!,?)*/6\6<VKB8*\AS
MV8B,J[?T^J3":[G6ZZ[7ZLB#+)!_2\F\*Z<@.K+9@.#*4R',G,* \9@.G*MPZ\EZ
M2\4JS)X!Z'U!_,6Y"LF1VY2F/*(^3+RS6Z*E*\-K;+J$G)>"Z\:3O,DKF<5Z
M;+R:#,H=[,NZ2J>>G+V7O+K)?,O-+,HK++_5M\J W,K&7,NPO,NI6ZN[3/^@.
MPTRZUCO&7,S+MUO 8LS*SJRYHYS"G&R[SZS(H/S#E_O.\DS'TDQ_?2S"PRS(
M])S,WQS$YCS0NBO0X/S)[7S#K7S//.R4J6O*S3N\]DS*[7RB`IW->^G,$WW-
MA3S#^DS-U!?+'[S(>+R]4ZS%)PR8U)O2)7V@.5IO(8PS'*HW$8:S-&JS +QW"
M_LN[WPO0"0JV3PRG$LS&$#W'B6S1<IRYN$O$#@.K2TV?$J<C4]YM_W6Q\4)W#
M1+JX^?S1J=Q]%AQ\>0R[5_VY4CS6_VG6?AS5L,O ^K?/]/O6-.G4<#W7E.C6
M!5C"CXC6=$V==EVU7^VL.@.S.!PUZ>KW7P]G7,"S_Q 2,JXQMV$R+V%V;QFM\
MQS\]H$H:P37]Q#-=V(ZMF9 =J1K-J<6[T<K[QY$LU9W]O'(=?<7\S-D;S^2L
MTW'LRYR=VIZ]VM#7VAL=V\#,VRX9SJAMVZK=U5X=VA3-T;W=R76)T;4MW#/Y
MV5W;TYS<TD!=T[RMTDVLH,/KW-D*W=S]W9R)V^ ]W@.WHW>1]WK IWNB]WOYG
MWO WULW-WI+HWFJ:U'KLP3;,B%!,W?O-UO+=H/2]V'1<VHM8H-D\W1O\WU,:
MX$/<T03NO6&<X,:=W'NLX "NWLX'TPTLTZ%,T#<<R!%MX9W*X".YS;0LVP^,
MR*(]R?$MXA")X;G=SX/]_\H8O.*G'=PN3K0P_GR-3,32VM!F#-O^G>/J2>*D
M)[U#/=-*C9=X[+ALS-]72^0,:N2@.+>523N4`;.5$CN5:WN6VM^->'N;.Q^5B
M7N:@.1^:$_=,ZO+G1_=<CF>)FSHYH?L4*G=\H7,%''.? ..>"C<5YGME<7,E^
MGMTK*LRGK.=TR.=.[N"++LGO',&4J]3H.,&:C.AU#>;I*^.X"LV$S.GCO-15
M'<.6'HR*ONFU/.,9+='Y#>K!#<^C/M^8SGP]GM?*'.*5'N*Y:^@.M_NKM'>N+
MRZY)GM(:[K7<Z\'$7MI-SNN73MSHM^O*'K&E;J+._NS=[>O4?NVE%^W8[N+:
M_O^U]XO9;KZ#82WK)?S4DOB_D=CM*1F+.%[CC$[22H[D^JOF/A[N]6WH1]Z2
M&MS#.UW%97VD+RWA6JS7:&VGMV[N^MW8(&CM8.W"F9O8FOZL' KW=%VS0AUZ&
M%Y^>0"ZYD_K#`^W#%A_8=Y[6@.*U]Z!YZZK[<!MF7^RW=9?W+USS+'?W-*MS%
M@.5[&Y/S%?HOSNPK,.(_/0'S/-%_QE;SSN;O9]@.WL28V_1RVX47Z]]TW4$![A
MD$[U"^K GY?ROZW.DI[K,-_S,:_A*!WQ8]_#-*Z_E,KSDGSCLUWH2L[ DVV7
M<-S-30_B9N_.-C[ANKRV/Z_;!:[<RBS,!P[06<_PP&?_S?Z\]M/]];BLR*A^
M]**+W]F-S#D?M[D<\;(LS@.\MZDM]]*$^VX8,Y[H]Z?L;Y""?TP)9\XZ/W;0[
MD.RNT<P,^D->B88?O3/,]:".T8R?^9!_XJM/\[SOZHW/]S/_R^G<\7!/TYZ/
MVK$KSH4KY$B*]Y O^ IL^M:?T77L\+7^VT#?>5H_Z/C,^QWN]4%?SH0M\::^
M_)%;Y[C>P+@..I9L_\YW_\2*?W,1\_>-_R2!O^94_X0D=S8"@.`*! *%AH2#@.X
MF(AHJ%CXR-AX2-B@.M\<T\D3)V>GY"1K*N3CIF @.0>;J(2LHJ>0I9ZJK:.DM[
MR$HJB IIN\NK^BH\JWO[VHH+_UR<FMNKW/L+W-CLVAQK'6RL34RIRSU*+!V^
M'/L+G;QZ;0Z++NR\JAP//P\N?XQH:UU\
M#)CPH<12HR9:O(@.QH\:-HOIEVL0QHZ^0!'F-))D,I<I@.)U=VD_8)ILN9-&O:
MK'3IX\V=/'OZ_ DTJ-"A+CW^(XHTJ=*E3)LZ=6H4Y-.I5*M:O8J5:M2L7+MZ
M_0HV[,"M8LN:/8LVK4^R:MNZ?0LW+BBV<NO:O8O7*MV\?/OZ_3MS+^#!A L;
M!BCXL.+%C/DF;@.PYLN2RCR=;OHRY:>7,G#M[MKGYL^C1I">&+HTZM6I/IU>[
M?CVZ-?_LV;0GRZX--I?NW;Q[^_X-/'A+W&AO$^\*P(7RY<R;.W\./;KTZ<X?
M%#QNUCAVK,D/>/\./KSX\>3+FS\/OHKU[6VULZ_:G:OZZ^^_NJ__-+ZI1_SW
M^^\/X'\"!KC(?/B===^!3,5'GU*#&*B@.6 E&F)1^6$%(H7TY'96A5PQ>E$\Y
M$SVX7H=>36AB4!:.6$XZ&6&8(E8HQNC3AQ*1$]&-"L!(8U4S]KC3B@._AV*!#
M/ +YU(](UF3CD-WLHA&)12Y)E))4NB2D0SA2--&15RIEY9<H->FD)"Y
M4&THE9H.NG" 2.*(
MGU,2E2:C>+(IJ5#Z$3A@.IIANJBDBB%9:TZ*@.*I0E59^.6A2EJ /:47!6NO@.IK
MK++.2FNMMMX:*Z"KWB3JKA ]`&RPP@.Y+;+'&'HMLLL4^ZNM&O38;BG#23DMM
MM=""INJUVB+Y[+;>BM;MM^)F%NZXYDI6[KGJ+I;NNNX2UNZ[\ O85[[SVVE7O
MO?J^E>^^_A:7[;\"8];/!4P\H8D`"B_,\,)$/ QQQ!)/3''%%E^,<<8:;\QQ
MQQY_#'+((H],<LDFGXQRRBJOS#(1#0QQR0!ZS$QSS3;?C'/..N_,<\\^_PQT
MT$(/37311A^-=-)*+\UTTTX_#;71*GM,37755E^-==9:;\UUUUY_#7;88H]-
5=MEFGXUVVFJOS7;;;K\-=]J!```[
`
end
Couple simple questions:
1. Are the English PC's on a different subnet by any chance?
2. Can you ping the SQL Server from the English PC's?
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:eFIMjgStEHA.904@.TK2MSFTNGP11.phx.gbl...
> hi guys im having troubles to connecto to sql server, my clients are win
xp
> and win 2000 pro, before i had the sql server 2000 on a windows 2000
server
> and all worked fine, but two days ago i changed to windows server 2003
> standard and the problems began...
> when i try to connect to sql by odbc or by another way its the screen that
> appears, the extrange is that in downstair there are 4 pcs and that 4 can
> connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
> spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
> english and just 1 XP in spanish can connect the other 2 not, i thought it
> was a problem with the server but now i connect a new laptop with winXP
> spanish SP2 and it works fine... so i dont know what to do, all pcs have
> mdac 2.8
> now i thought its problem with clients but i cant find difference between
> pcs except for the language
> what can be?
> i tried to connect by IP, i checked the port and nothing works =(
>
>
cant connect xp pro sp2 to database on ntserver 4
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a login
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?
managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and hey
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:
> We have a program using sqlserver7, bde 5.01, msde, which works fine on the
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a login
> screen, where it then fails to connect to the database with a generic cannot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?
cant connect xp pro sp2 to database on ntserver 4
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a logi
n
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and he
y
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:
> We have a program using sqlserver7, bde 5.01, msde, which works fine on th
e
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a lo
gin
> screen, where it then fails to connect to the database with a generic cann
ot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?
Sunday, February 19, 2012
Cant connect to SQL Server 2005 Express from VStudio 2005 pro.?
I can't do subject. It says the SQL Server does not allow remote connections, but in SQL Server surface area conf. it is turned on.
What to do?
CheersGot it to work now. I wrote localhost as with SQL Server 2000, and changed it to .\SQLExpress
Cheers
cant connect to Sql server 2000 sp3a in windows 2003 server
and win 2000 pro, before i had the sql server 2000 on a windows 2000 server
and all worked fine, but two days ago i changed to windows server 2003
standard and the problems began...
when i try to connect to sql by odbc or by another way its the screen that
appears, the extrange is that in downstair there are 4 pcs and that 4 can
connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
english and just 1 XP in spanish can connect the other 2 not, i thought it
was a problem with the server but now i connect a new laptop with winXP
spanish SP2 and it works fine... so i dont know what to do, all pcs have
mdac 2.8
now i thought its problem with clients but i cant find difference between
pcs except for the language
what can be?
i tried to connect by IP, i checked the port and nothing works =(
begin 666 error.gif
M1TE&.#EA!P+&`.8``````.5($P!+YP`DI@.`.?7BH]%MDJ_'OXK$M"B)T]>OH
MUV-OA@.!BZ0`[X =$P7%O9)FWU.A^929#<2\\(,KH_P!F_P!:YP`?TK;8\0@.A
MDC.9_^?U_XVJQ !0WCA2L !F_^_8TN9J38V5GA9J[L/%O]5*)0!;\ !3YJ;-
M\WF:O `FK ``2 H8@.QHO6/___^5>-TZ&W^R1>4.$[4)6=]4U!"&)_P!*W-[H
M\["TM,O<^0!9^)RBS-K9S!,D3%2/\0=R_7"*M.[O]HJ;T 4VM@.!,[QM0OCI%
MF_"FE)B[]KO(Z0)D]1DFB@.@.QV*W"V4ANM@.A5W0`SF:>LKH"HV@.%(T0`[TJRH
MF=]3,$-CF^;HZP!S_2N0__'Y_YB=I-W?[0!1\-?L_VB"S*TY'+W W2DZF7)^
MDP`@.R-[O_P!#W'N:R-5%&YNJV1J"_X>T^^9E0RL_8KC<_P`SS D<BN50(N=S
M63^7_P!@.[EEUQ@.!#S]?>W4I5HP`>H `3C&:9__.[K;/!S/___R'Y! 44`'\`
M+ `````'`L8```?_@.!."@.E.%-H>''1T6C!8,#(V1DI.4E9:7F)F:FYR=GI8F
MH:*CI*6FIZBIJJNLK:ZOKY^RL[2UMK><7EXG)P*^O\#!5 K$Q(.%2C]KRVM:
MSG30T=+3U-76U]C9VMO<W=[?X.'BX^3EYN?HZ>KK[.?.[UHU-6L_5'#%A!9*
MR<QK\O!:- @.$2+"@.P8,($RI<R+"APX<0(TJ<2+&BQ8L8,VK<R+&AO(\@.0_;K
M]^.'B6$*)MQ1]*AELI)98LJ<&;/D#YHX<^K<R;.GSY] @.PH=2K2HT:-(DRH%
M6J&ITZ=0HTJ=2K6JU:M8LVK=NG7GOJ\ZPH:M0[9L'5XG0IVXT R#EG3N2_USN
MLTFWY->[>//JW<NWK]^_@. ,+'DRXL.'#B!,K7LRXL>/'D"/C;0DI$EJTBA0A
M0G0'CAX%<&Q,R=R(\J.[ILO"6LVZM>O7L%GAFDV[MNW;N'/KWBW+AQD7P(,+
M'^X"S%LXR/4@.?ZNHM.GGE'E+GTZ]NO7KV+-KWR[KLG<?"F)$F!.BC?D7Z%]8
M66\EC1408)"K4*%G`!SFBQA!-TW)N___``8HX( $%FC@.@.0@.FJ.""##;HX(,0
M&IC9A!16:.&%&&:HX88<=NCAAR!JZ$(,1Y0H7@.0HCC<'>>594 4()-\@.W``'*
MW=><?OL]TE^$//;HXX] !BGDD$0&&.*12":IY/^23';H0@.0E'A'#B2FJ6-X+
M)83A@.HPT(G>(<SGJ*$F19)9IYIEHIGEFDVRVZ>:;;+HPAXDGK LAB>6VHE^66
M<)0QHW)4V'#C?I>H:>BAB":JZ**,-HKHA2Z$,&4,(,A)WGDON-#'>GO:4X8*
M!)0!1Z =G, (!@.FTE `&+>60PR1 8N!"#@.(BL8$+** U`@.K H3 "+\#5>FNN
M9@.:[H*N.)JOLLLPVBU8P`D0:@.7C!A7!EIL!QJJ6G,Y9!Q1EGH &6!"T(\\0@.;
M+D#QB*L9P-HC$BYXP$(&;'SAGZQ%&!%$$[QLD,,`2^ 1Q!,G`,<"@./CJRV^9
M!A^;0P;.1BSQQ!3["*W_"VU4&5R>V+H@.AQPN;GO!IZ%^&RXO) KC0Q1"/_,9"
M2QED0-:8/!H\1<$N0'R9P:+%,0"Z>4 L@.PL[=-#P?SQ/X3/#+AR\8,P51RWU
MU%0_&PS&*:X87,<?]SIR*!Z>T9^%B0`W!AUF.V"$74$1U8!7[CPA0R,`(>$
MO2? ZP(2O,B0@.]R_YFTWL,'A;"Q:<>]P6=PLW %L%RH<[5_BWNG--^%WG_#W
MKR/,*OC>:-F-=^A-5SXX+[+Z6X#AP*)P*P:!5RW[[+2K"8P++]BY8@.C#=>WU
MME1<$#85OS R=!="6,#L_T7;3!;@.@.109-`#'%N"X8X 2]+MB1![D6W#H&
M_QY =("N]^!CSP(+ZK/?B Q!N' #W>HW`EP&!E<"O_STPPO&]VJH6_:VYP-R
MF2][:B@..``6HO7;9KVF1.-_WDB<K#QC!!6(80OV DR\7)(%L-*N="$=(0@./I
MXH3 >D$(=&>MX%C!=W+84P,
M`$8TV%MNU3@.7!&$(<3/""3+@.`";>P8E);%HH#%:*)X@.!.#!(F1:WV#0NGL*+
M8#0!$QV 13$V[@.XF",(3-Q $%L2/!6Q\HAO?,@.HSAL**6.09< ;@.1C<:S06$
MC(TB%\G(1CKRD9",I"09><)*>L$%5EBAG7@.G'!BF`?\!+IAA# 2\P0Y29('IC
MR)X+4@.D$!PRQC$T+BRC,R$7@.Q"$!7<!5`@.IIRT+ZLA0)#,(=X K:$4'2N"RSP
MXRF"><7AQ.&7T=L!$.- G&<JDXPLZ*,6;1E%L^$AF[7<YA@.G2<YRFO.<Z$RG
M.EMA24RVP5HM!$X;@.M.U`'PRE#-4P1Y(V8"TA.(-36/>#9(I!E<:C(EX,=@.^
M$.I$%BCA!'9PX@.D86L=7.M2B?+$EN@.P0B@.+N`']-^XLMF;B^]6%T'YT#SA*J
MV+22.E2A"0WI5RC*`K6Y``-CR !&%0K3O(CEIT -JE"'2M2B&O6H2$VJ4I?*
MU*8Z]:E0C:I4IXK4$WKL!>__Y"3&\D3/`'@.5E#-L@.#Y)Z8NR`)0%Z!("_L0`
MA1\8+'I 4 (*V+ /F&Z4#^2*PQOHZL0XW#6O)T7H79"0`R68;0<.#4(7IC""
M+P1A"4/H*5X(:UBBL0"N...@.`74^Z#W@.A]I1 S.QF)5M7F>[CKT*(P]^,L+X!
MG&"G(26M9&9+V]K:]K:XS:UDB.J"-&!UGO+D6,>\2@.-0^J(!<-AG`P1@.@.;(8
MS&QC8&.ZW-JT"D@.AEU\HPA XFT#IL6 (!9S5&.*@.A.Y*X;LG#2]>$I $%V@.6
MO0GXXMGB\#SAK+>][]VN%.)W@.S%L5[):6-MVE;!?^?F7LU\ASC[,^UU>!><+
M/H#M_TM-J]L*6QBW7,FPAC?,X0Y[F"L_[:T5L-J'K0I7#IHB+BB)0 3D*E<`
MHMC'^G[ @.)?]8,8W9D%)')"!>=6A*>M[RA#6YX"F3&%],FO*D/'HE" ;V<E.
MJ<,`6!"'(C=%RDL(`A!^7 &70OG*4ZZR4QP0!Q\#F050L0#[QESF)'<9S5'Q
M,IR77.0$V&%]J0S"%-Y\YCY_^,^ #K2@.!TWH0AOZT(<.2V]!EIY&OZ">*G8!
MBUU,5A/@.I2Z8ODE-;(+H#(] FB[H-*+?L($$5 "O>(B#J%...ZE:[^M6PCO56
M7$"#-)2 /;C^F%>)6UQ)MSBYE;YTINLBDV$;^]C(3C:FE?^P9&4[^]G01K8:
MXF<&),PKVB61M;:WS>UN>QO19BA!&L;]HG*/>]PT2'>ZM31I8"\W%'DY=K&S
M_>UZ_YG9;1Z"O?...[W[[^]]1X0,(PH" @.AO\X @./`PCXT.X7ER+>] :XQ"=.
M\8I;_.*O!DM8\$J<C@./'#'S0A0`HO5P!F*H19-'+5"[,\I8S!N,PY[#+9T[S
MP!BUDC^U)(MWOG.2-\ &5'C+6S:3B Q!Z^A(3[K2E\[TICO]Z5"/NM2G3O6J
M6_WJ6*\ZN+;.]:Y[_>M@.#[O8QT[VLIO][&A/^QD$(/:PAE7L5(C[#-W]<Z';
M_>YXS[O>]\[WOOO][X /O. '3_C_PAO^\(A/O.(7S_C&._[QD(\\X>>^!R:,
MX G%R+SF-\_YSGO^\Z /O>A'3_K2F_[TJ$^]ZE?/^M:[_O6PC[WL9T_[U#=@.
M`)6_?.UWS_O>^_[WP ^^\(=/_.(;'_6WSSWFC\_\YCO_^="/OO2G3WW3)]_R
MRZ^^]K?/_>Y[__O@.+_[U=1_^\IO__.A/O_JA/_[LK__]\(^__.<__P;H0?GT
MS[_^]\___A/?_OCG?P(X@. 18@. :H>0"(?0>X@. S8@. X8?@.E(?@.\X@.118@.1;H
M>Q'H?A>X@.1S8@.1[H>1FH>GC0!5A0@.B98@.B3 `Q^X@.BS8@.N 7@.J9'`@.(C1Q[G
M`EN `RKH_X(ZN(,\*'[WIX"EAP7 L07"X0<X0(1#2(0W.( ```">YX2?!X4]
M.(542'LP*'IX@. 4T*!PSL (KT -(F(081 *OUX1-.'M2*(6BIX::YX1LN'EO
M6(5R.(>G=X6@.EX58$(; @.0<KP )[L ) ,!Q;$ 1;D ,XT'IQ"'N)&'J+2 R-
MJ "/2(>2.(F99X>>AP=9]B> ,K``4P``4)M 6B.(0WL 5-<(BJ%X=FZ(BK
M"(FMZ(II>(:K"(6M
M4 0P``8VN 4;$(W L0$WL $I0(:I]X9IN(NZN(W>F'G?^(O;V/^+G.>&W4B.
MXQB)PKB.+DB,FX>)S/.,R:B'TQB-]DB$-W #.4 &.7AZVHB.`"F.OJB&X7B.
MOTB.O3B+W3B0",F.#CF'[IAYF-@.%MS*/HR@.<]AB-9K"19B"*.6 &"\ %V0B'
M`6F0)GF0*&F.XMB0W/B-*MF0ZOB0,MF!$5D,8H 'I0B-&;D%0" !/BD!*Y "
M6\"11+D%7Y #3; `_6AZMUB2+_F4W-B24CF.*0F04)F.,YF5[?B#$MAY?H"3
M.KF3J44`<1 '!""4'/D%:OD%&W"42> &J(AZOLB+4XF0KXB+NUB++$F0"DF+
MN0B+M*B5@.OF!-4D,?B &U:B11;D%.07_!7N !D.YEI))`4F0!"T@.`H.9F9J9
M?H6I`(=9C419E%<0!U# `I IF9*9`Y5YF9O9FJ[9?9UYF!])E)*Y!:-9FFC0
MEA2PF[Q)`:IIF9CYFL(YG,\7FWXPFZBIEAMPFZ:Y`;W9FZK9! *Q)G-19G<+7
MF1#@.!TF0G&NYG*39G,_)FTG0!! PG>H7DTQIG>I9?URI@.9OG!_"9`VH9GF;
MG+D9GA2 `4W0!%=@.GDQYEW]YBPK9>>B9EW\9E0`:BX&YG@.RZ?IW)`TW@.!TT@.
MG_1IGV; FV^0H6^ `N0I`7 IER1YD 39AD]8>E#IBC!9ERO9H"QZ?IVI`!P`
MGTF0`^&YG'L`_P4$``3.J:$9B@.(0``$&T -*":+@.2*(C"HZYB(M^295%6I55
M69 %VJ)26ISM&7H\D (<``$S^IPX!05>.@.880 $\ZJ,0D (]X 8BF8U):J1M
MN*8D294+2J).JJ(F&:53>J?&]Z(*@. ,<D*5-$*84\ 5H0"-%4*A%``52(*8;
M^J-H( $MP(^(&)4G6:1\*8L)^8KEF*)/ZI1XVJG;IZ<*P 58ZJ<8D*%(L*$H
M@. *HB@.%D6J82(*38R'HON
M^J/"Z@.0](*1Q*:M.FHB[&JTHV:12N:FT:J>]FJU66*6D%P4+$*S"VO^G$)"J
M9-JG/7FF9-"L<HFI">J&`,J*2;JD+(FD"GJI]@.JOVIJOS/>KQ$ "9# #,T &
M*3"P6)JJ4@.`$5_"J+3 #(A"KM(>M^AJQ$\BOQ, #.$ &"S #;B !P8H$*" %
M+7"F"]"P2UE[!RJQ*$N8W'IZ/-"R) "P/_JQ+; `.."P*7NSPDFQG$<";@.`$
MXRH%
MKE>I]\J*37NS3\MY/$ &5["TL?>/(IJINZ>U6VNK=AFV.#NVG1<%Z8J&<EJ2
MU'JOYIB.:WJD5FF@.@.1FG>SNOLRJW$DNWPZ?_EY1*H&ZZD-8*N?3JEV [E;<Z
MK2C:I%R+N-JJN,5WN(?[I@.P9D+88NDTYIZ$;HGD+IYRKKYY+?*"+M6RZMRIY
MNH7+NK1:HB$*N&[;NCF[LN$7IX2;J06)NEAKNZP+N-1:O-7JN[WZNK_'M>TZ
MN7R;MW2IC:.+H(][O $:KTKJO)T+O.G7N^!;OM0'O<UWLN:[OBXJONS[OD[K
MOO [OX*)OKV'J;QWLK.HOE.XO^2+B/R[?__KC\W+?_:;OPF9P -<P),ZO?!:
MJ0+:O9?[P&B(OY@.[>D_IP $*F.XZH/@.JO5F+MQ?\A &<GB%<M<L[K_EWP&V;
MP)6KB(:+H'&[MC2L_[J:JHH(/,(@.BKO>R+QS6L-8V<(F++M#O,!L:[S]Q\(F
M&[BU:ZGRBJ_7*XL;?*NS>I6Z&\,XW*:#6ZUZJ;Q]6Z=0;,73:L5;K+JGF[SE
MZ+U+6J\?;*E1O+T+*<$4G,)PJ,9S?+7^*ZD3+']*_+!,?)*/6\6<VKB8*\AS
MV8B,J[?T^J3":[G6ZZ[7ZLB#+)!_2\F\*Z<@.K+9@.#*4R',G,* \9@.G*MPZ\EZ
M2\4JS)X!Z'U!_,6Y"LF1VY2F/*(^3+RS6Z*E*\-K;+J$G)>"Z\:3O,DKF<5Z
M;+R:#,H=[,NZ2J>>G+V7O+K)?,O-+,HK++_5M\J W,K&7,NPO,NI6ZN[3/^@.
MPTRZUCO&7,S+MUO 8LS*SJRYHYS"G&R[SZS(H/S#E_O.\DS'TDQ_?2S"PRS(
M])S,WQS$YCS0NBO0X/S)[7S#K7S//.R4J6O*S3N\]DS*[7RB`IW->^G,$WW-
MA3S#^DS-U!?+'[S(>+R]4ZS%)PR8U)O2)7V@.5IO(8PS'*HW$8:S-&JS +QW"
M_LN[WPO0"0JV3PRG$LS&$#W'B6S1<IRYN$O$#@.K2TV?$J<C4]YM_W6Q\4)W#
M1+JX^?S1J=Q]%AQ\>0R[5_VY4CS6_VG6?AS5L,O ^K?/]/O6-.G4<#W7E.C6
M!5C"CXC6=$V==EVU7^VL.@.S.!PUZ>KW7P]G7,"S_Q 2,JXQMV$R+V%V;QFM\
MQS\]H$H:P37]Q#-=V(ZMF9 =J1K-J<6[T<K[QY$LU9W]O'(=?<7\S-D;S^2L
MTW'LRYR=VIZ]VM#7VAL=V\#,VRX9SJAMVZK=U5X=VA3-T;W=R76)T;4MW#/Y
MV5W;TYS<TD!=T[RMTDVLH,/KW-D*W=S]W9R)V^ ]W@.WHW>1]WK IWNB]WOYG
MWO WULW-WI+HWFJ:U'KLP3;,B%!,W?O-UO+=H/2]V'1<VHM8H-D\W1O\WU,:
MX$/<T03NO6&<X,:=W'NLX "NWLX'TPTLTZ%,T#<<R!%MX9W*X".YS;0LVP^,
MR*(]R?$MXA")X;G=SX/]_\H8O.*G'=PN3K0P_GR-3,32VM!F#-O^G>/J2>*D
M)[U#/=-*C9=X[+ALS-]72^0,:N2@.+>523N4`;.5$CN5:WN6VM^->'N;.Q^5B
M7N:@.1^:$_=,ZO+G1_=<CF>)FSHYH?L4*G=\H7,%''.? ..>"C<5YGME<7,E^
MGMTK*LRGK.=TR.=.[N"++LGO',&4J]3H.,&:C.AU#>;I*^.X"LV$S.GCO-15
M'<.6'HR*ONFU/.,9+='Y#>K!#<^C/M^8SGP]GM?*'.*5'N*Y:^@.M_NKM'>N+
MRZY)GM(:[K7<Z\'$7MI-SNN73MSHM^O*'K&E;J+._NS=[>O4?NVE%^W8[N+:
M_O^U]XO9;KZ#82WK)?S4DOB_D=CM*1F+.%[CC$[22H[D^JOF/A[N]6WH1]Z2
M&MS#.UW%97VD+RWA6JS7:&VGMV[N^MW8(&CM8.W"F9O8FOZL' KW=%VS0AUZ&
M%Y^>0"ZYD_K#`^W#%A_8=Y[6@.*U]Z!YZZK[<!MF7^RW=9?W+USS+'?W-*MS%
M@.5[&Y/S%?HOSNPK,.(_/0'S/-%_QE;SSN;O9]@.WL28V_1RVX47Z]]TW4$![A
MD$[U"^K GY?ROZW.DI[K,-_S,:_A*!WQ8]_#-*Z_E,KSDGSCLUWH2L[ DVV7
M<-S-30_B9N_.-C[ANKRV/Z_;!:[<RBS,!P[06<_PP&?_S?Z\]M/]];BLR*A^
M]**+W]F-S#D?M[D<\;(LS@.\MZDM]]*$^VX8,Y[H]Z?L;Y""?TP)9\XZ/W;0[
MD.RNT<P,^D->B88?O3/,]:".T8R?^9!_XJM/\[SOZHW/]S/_R^G<\7!/TYZ/
MVK$KSH4KY$B*]Y O^ IL^M:?T77L\+7^VT#?>5H_Z/C,^QWN]4%?SH0M\::^
M_)%;Y[C>P+@..I9L_\YW_\2*?W,1\_>-_R2!O^94_X0D=S8"@.`*! *%AH2#@.X
MF(AHJ%CXR-AX2-B@.M\<T\D3)V>GY"1K*N3CIF @.0>;J(2LHJ>0I9ZJK:.DM[
MR$HJB IIN\NK^BH\JWO[VHH+_UR<FMNKW/L+W-CLVAQK'6RL34RIRSU*+!V^
M'/L+G;QZ;0Z++NR\JAP//P\N?XQH:UU\
M#)CPH<12HR9:O(@.QH\:-HOIEVL0QHZ^0!'F-))D,I<I@.)U=VD_8)ILN9-&O:
MK'3IX\V=/'OZ_ DTJ-"A+CW^(XHTJ=*E3)LZ=6H4Y-.I5*M:O8J5:M2L7+MZ
M_0HV[,"M8LN:/8LVK4^R:MNZ?0LW+BBV<NO:O8O7*MV\?/OZ_3MS+^#!A L;
M!BCXL.+%C/DF;@.PYLN2RCR=;OHRY:>7,G#M[MKGYL^C1I">&+HTZM6I/IU>[
M?CVZ-?_LV;0GRZX--I?NW;Q[^_X-/'A+W&AO$^\*P(7RY<R;.W\./;KTZ<X?
M%#QNUCAVK,D/>/\./KSX\>3+FS\/OHKU[6VULZ_:G:OZZ^^_NJ__-+ZI1_SW
M^^\/X'\"!KC(?/B===^!3,5'GU*#&*B@.6 E&F)1^6$%(H7TY'96A5PQ>E$\Y
M$SVX7H=>36AB4!:.6$XZ&6&8(E8HQNC3AQ*1$]&-"L!(8U4S]KC3B@._AV*!#
M/ +YU(](UF3CD-WLHA&)12Y)E))4NB2D0SA2--&15RIEY9<H->FD)"Y
M4&THE9H.NG" 2.*(
MGU,2E2:C>+(IJ5#Z$3A@.IIANJBDBB%9:TZ*@.*I0E59^.6A2EJ /:47!6NO@.IK
MK++.2FNMMMX:*Z"KWB3JKA ]`&RPP@.Y+;+'&'HMLLL4^ZNM&O38;BG#23DMM
MM=""INJUVB+Y[+;>BM;MM^)F%NZXYDI6[KGJ+I;NNNX2UNZ[\ O85[[SVVE7O
MO?J^E>^^_A:7[;\"8];/!4P\H8D`"B_,\,)$/ QQQ!)/3''%%E^,<<8:;\QQ
MQQY_#'+((H],<LDFGXQRRBJOS#(1#0QQR0!ZS$QSS3;?C'/..N_,<\\^_PQT
MT$(/37311A^-=-)*+\UTTTX_#;71*GM,37755E^-==9:;\UUUUY_#7;88H]-
5=MEFGXUVVFJOS7;;;K\-=]J!```[
`
end
There is a way to find out - I think you should find out if the clients are
using "Named Pipes" or TCP/IP for connectivity.
Bring up the ODBC connection, then on the second page you should see a
button "Client connectivity". Go into this and make the bullet TCP/IP.
Please let me know if this fixed your problem.
=-Chris
On the clients that cannot connect, click the box "Client configuration"
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> hi guys im having troubles to connecto to sql server, my clients are win
xp
> and win 2000 pro, before i had the sql server 2000 on a windows 2000
server
> and all worked fine, but two days ago i changed to windows server 2003
> standard and the problems began...
> when i try to connect to sql by odbc or by another way its the screen that
> appears, the extrange is that in downstair there are 4 pcs and that 4 can
> connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
> spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
> english and just 1 XP in spanish can connect the other 2 not, i thought it
> was a problem with the server but now i connect a new laptop with winXP
> spanish SP2 and it works fine... so i dont know what to do, all pcs have
> mdac 2.8
> now i thought its problem with clients but i cant find difference between
> pcs except for the language
> what can be?
> i tried to connect by IP, i checked the port and nothing works =(
>
>
|||Chris thanks a lot, but ive found other way to solve it, i know maybe its
not the more correct but i reinstalled the Sql server because i found at
microsofts web a tool to check the ports, its name is PortQuery, with it
you can check for Sql server if it is running on a server, or network
connectivity and other things, i saw that the server doesnt aswer to the
tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
server, and it solved the problem =)
the tools url is http://support.microsoft.com/kb/310513/EN-US/
Rick =)
"Christopher Conner" <someone@.someplace.com> wrote in message
news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
> There is a way to find out - I think you should find out if the clients
> are
> using "Named Pipes" or TCP/IP for connectivity.
> Bring up the ODBC connection, then on the second page you should see a
> button "Client connectivity". Go into this and make the bullet TCP/IP.
> Please let me know if this fixed your problem.
> =-Chris
>
> On the clients that cannot connect, click the box "Client configuration"
> "Rick" <ricardo.blanco@.indap.com.mx> wrote in message
> news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> xp
> server
>
|||Rick, thanks for the tip about the tool.
Because you had to reinstall to fix it, tells me that next time you have
this problem, on the SQL Server itself, bring up the Server Network Utility
(located in Programs->Microsoft SQL Server) and double check that on the
enabled protocols list that TCPIP and Named Pipes is listed. I am betting
that they were not previously. If you want to stop clients from connecting,
this is the place to do so as you would just remove the protocols.
Cheers!
=-Chris
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:eN8LyBWtEHA.2788@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Chris thanks a lot, but ive found other way to solve it, i know maybe its
> not the more correct but i reinstalled the Sql server because i found at
> microsofts web a tool to check the ports, its name is PortQuery, with it
> you can check for Sql server if it is running on a server, or network
> connectivity and other things, i saw that the server doesnt aswer to the
> tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
> server, and it solved the problem =)
> the tools url is http://support.microsoft.com/kb/310513/EN-US/
> Rick =)
> "Christopher Conner" <someone@.someplace.com> wrote in message
> news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
win[vbcol=seagreen]
can[vbcol=seagreen]
pro[vbcol=seagreen]
have[vbcol=seagreen]
between
>
Can't connect to SQL Server (developer edition) from another PC?
SP2 machine. It's installed without any problems.
When I try to connect to it from another XP SP2 machine (by creating
an ODBC data source) I get a Login error:
[ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
Connection failed: SQLState: 08001 SQL Server Error: 17
SQL Server does not exist or access denied
I can ping the server fine from the other machine, and I've tried the
standard "sa" user/pw as welll as my own logins.
The server is configured for mixed authentication (Windows/SQL
Server).
Can anyone suggest what the problem might be?
TIA for any help
IanAre you running XP firewall on that machine? If so, turn it off and any
other firewall (Norton Internet Security, etc).
Chris
"ITM" <itm@.nospam.com> wrote in message
news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com...
> I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
> SP2 machine. It's installed without any problems.
> When I try to connect to it from another XP SP2 machine (by creating
> an ODBC data source) I get a Login error:
> [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
> Connection failed: SQLState: 08001 SQL Server Error: 17
> SQL Server does not exist or access denied
> I can ping the server fine from the other machine, and I've tried the
> standard "sa" user/pw as welll as my own logins.
> The server is configured for mixed authentication (Windows/SQL
> Server).
> Can anyone suggest what the problem might be?
> TIA for any help
> Ian|||On Sun, 20 Mar 2005 08:59:30 -0800, "Chris Schmidt"
<schmidtc@.KvalleyDotCom> wrote:
>Are you running XP firewall on that machine? If so, turn it off and any
>other firewall (Norton Internet Security, etc).
>Chris
>"ITM" <itm@.nospam.com> wrote in message
>news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com...
>> I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
>> SP2 machine. It's installed without any problems.
>> When I try to connect to it from another XP SP2 machine (by creating
>> an ODBC data source) I get a Login error:
>> [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
>> Connection failed: SQLState: 08001 SQL Server Error: 17
>> SQL Server does not exist or access denied
>> I can ping the server fine from the other machine, and I've tried the
>> standard "sa" user/pw as welll as my own logins.
>> The server is configured for mixed authentication (Windows/SQL
>> Server).
>> Can anyone suggest what the problem might be?
>> TIA for any help
>> Ian
>
I've tried turning off XP firewall but it made no difference. I'm not
running Norton, but am using AVG anti-virus (free edition). No other
firewall/AV software installed.
Ian|||What happens when you telnet to port 1433 on that machine (or whatever port
you're running it on)?
Chris
"ITM" <itm@.nospam.com> wrote in message
news:0qbr315sngsoq0eh8eook7v1t5k3d5bcsr@.4ax.com...
> On Sun, 20 Mar 2005 08:59:30 -0800, "Chris Schmidt"
> <schmidtc@.KvalleyDotCom> wrote:
>>Are you running XP firewall on that machine? If so, turn it off and any
>>other firewall (Norton Internet Security, etc).
>>Chris
>>"ITM" <itm@.nospam.com> wrote in message
>>news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com...
>> I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
>> SP2 machine. It's installed without any problems.
>> When I try to connect to it from another XP SP2 machine (by creating
>> an ODBC data source) I get a Login error:
>> [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
>> Connection failed: SQLState: 08001 SQL Server Error: 17
>> SQL Server does not exist or access denied
>> I can ping the server fine from the other machine, and I've tried the
>> standard "sa" user/pw as welll as my own logins.
>> The server is configured for mixed authentication (Windows/SQL
>> Server).
>> Can anyone suggest what the problem might be?
>> TIA for any help
>> Ian
> I've tried turning off XP firewall but it made no difference. I'm not
> running Norton, but am using AVG anti-virus (free edition). No other
> firewall/AV software installed.
> Ian|||On Sun, 20 Mar 2005 09:41:09 -0800, "Chris Schmidt"
<schmidtc@.KvalleyDotCom> wrote:
>What happens when you telnet to port 1433 on that machine (or whatever port
>you're running it on)?
>Chris
>"ITM" <itm@.nospam.com> wrote in message
>news:0qbr315sngsoq0eh8eook7v1t5k3d5bcsr@.4ax.com...
>> On Sun, 20 Mar 2005 08:59:30 -0800, "Chris Schmidt"
>> <schmidtc@.KvalleyDotCom> wrote:
>>Are you running XP firewall on that machine? If so, turn it off and any
>>other firewall (Norton Internet Security, etc).
>>Chris
>>"ITM" <itm@.nospam.com> wrote in message
>>news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com...
>> I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
>> SP2 machine. It's installed without any problems.
>> When I try to connect to it from another XP SP2 machine (by creating
>> an ODBC data source) I get a Login error:
>> [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
>> Connection failed: SQLState: 08001 SQL Server Error: 17
>> SQL Server does not exist or access denied
>> I can ping the server fine from the other machine, and I've tried the
>> standard "sa" user/pw as welll as my own logins.
>> The server is configured for mixed authentication (Windows/SQL
>> Server).
>> Can anyone suggest what the problem might be?
>> TIA for any help
>> Ian
>> I've tried turning off XP firewall but it made no difference. I'm not
>> running Norton, but am using AVG anti-virus (free edition). No other
>> firewall/AV software installed.
>> Ian
>
Have just downloaded and installed SP3 for SQL Server - it seems to
have done the trick. Should've tried that before :-(
Thursday, February 16, 2012
Cant Connect to server //SQEW..? WHAT IS THE PROBLEM?
so my problem is when im trying to connect
to my database in SQL server
that error is something like this :
Unable to connect to server //SQEW
Server : msg17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server Does not Exist or Access Denied
am i have to Add Network Library Configuration
in SQL Server Network Utility
because when i want to add it
in winXP <-- mine
network libraries for shared memory is disable
but for the named pipe is able and something like this
is define as pipe name --> \\.\pipe\sql\query
but in my friend pc ,he use windows 98
in network libraries network libraries for shared memory is
able but his named piped is disable
how i can connect it to the SQL Server?
is there any confoguration method?If you have the IP of the machine runing the SQL Server, use it instead of the name.
Go to the enterprise manager and ad the server there using the IP.
______________
Paulo Gonalves|||Is i't really //SQEW and not just only SQEW ?
Tuesday, February 14, 2012
Can't connect to server - real newbie here
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!
Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Can't connect to server - real newbie here
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Sunday, February 12, 2012
Can't connect to MSDE
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
Jeff
By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>
|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
Can't connect to MSDE
SQL Server 2000 is installed on the server box, as well as MSDE for the defa
ult
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but tha
t's
as far as it can get. When I try to add the instance under a new registratio
n, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connec
t
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know),
but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but tha
t would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the de
fault SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is runn
ing MSDE.
> The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in
the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to a
dd the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphras
ed).
> I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance
> running on the workstation, although I can connect to the server's instanc
es (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can conn
ect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don
't think packets are
> being blocked. Just in case I created a temporary packet filter allowing a
ll packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, yo
u
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe
is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
Can't connect to MSDE
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
>> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
>> SQL Server 2000 is installed on the server box, as well as MSDE for the
>> default SharePoint and SbsMonitoring databases (SBS setup created those).
>> The workstation is running MSDE. The problem is that I can only connect to
>> the workstation's MSDE from the
>> workstation. EM on the server can see the MSDE instance (the worksation's
>> machine name appears in the Add SQL Server Registration dialog box), but
>> that's as far as it can get. When I try to add the instance under a new
>> registration, I get 'access denied or server doesn't exist' (paraphrased). I
>> also can't connect via EM to the workstation's MSDE from within a Win98
>> VirtualPC instance running on the workstation, although I can connect to the
>> server's instances (both SQL Server and MSDE instances) from within that
>> instance. I've compared the property sheets of all the instances to which I
>> can
>> connect from WinXP, and everything seems to be the same. Nothing shows up in
>> my ISA logs, so I don't think packets are being blocked. Just in case I
>> created a temporary packet filter allowing all packets from anywhere (risky,
>> I know), but it still didn't work. Still nothing in the logs. Does anyone
>> know what this might be?
>> TIA,
>> Jeff