Connectivity to FoxPro (dbf) from SQL 2005 on x64 Windows 2003

I have installed SQL Sever 2005 on an x64 bit machine running Windows 2003.
When I go to the ODBC Data Source Administrator, and click on the Drivers
tab, it only shows:
SQL Native Client
SQL Server
I would like it to show the "other" drivers that I see in other
installations - to connect to .mdb, .dbf, etc.
I tried installing MDAC 2.8, but it didn't affect the drivers shown in the
list.
Any suggestions? My goal is to write a SSIS package that connects to a
FoxPro (.dbf) file.
Thanks
PaulHi Paul,
There are two methods for connecting to Fox tables - OLE DB and ODBC. The
OLE DB data provider for VFP is only 32-bit compatible. There are no plans
to develop a 64-bit OLE DB data provider for VFP. I assume that the ODBC
drivers for VFP are also only 32-bit compatible (I'm not sure) but I am sure
that there won't be any new ODBC drivers for VFP.
Sorry to be the bearer of bad news.
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy@.cindywinegarden.com
"Paul in Denver" <Paul in Denver@.discussions.microsoft.com> wrote in message
news:F0E93714-1075-446D-AEF9-48D70D0834E1@.microsoft.com...
>I have installed SQL Sever 2005 on an x64 bit machine ...

> Any suggestions? My goal is to write a SSIS package that connects to a
> FoxPro (.dbf) file.

Connectivity Stand-Alone installer

Hi all,
I want my application's Installer to automatically install the SQL
Connectivity on machine in which the Connectivity does not exist. For this i
require a Stand-Alone installer (to be called from my Installer if
connectivity is not found).
Do you know if there exists a Stand-Alone Connectivity Installer?
Also how can i check if Connectivity is installed or not (from the
Installer)
Thanks
Shaun
Hi
MDAC is the client connectivity.
http://msdn.microsoft.com/data/downl...s/default.aspx
Current version is 2.8
Regards
Mike
"Shaun Camilleri" wrote:

> Hi all,
> I want my application's Installer to automatically install the SQL
> Connectivity on machine in which the Connectivity does not exist. For this i
> require a Stand-Alone installer (to be called from my Installer if
> connectivity is not found).
> Do you know if there exists a Stand-Alone Connectivity Installer?
> Also how can i check if Connectivity is installed or not (from the
> Installer)
> Thanks
> Shaun
>
>
|||Thanks that is what I needed.
Shaun
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:B25625E8-8D72-4A80-8A49-0F249B044998@.microsoft.com...[vbcol=seagreen]
> Hi
> MDAC is the client connectivity.
> http://msdn.microsoft.com/data/downl...s/default.aspx
> Current version is 2.8
> Regards
> Mike
> "Shaun Camilleri" wrote:
this i[vbcol=seagreen]

Connectivity issues

Hi,

I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

I have enabled all protocols , the sql browser is running , sql agent and sql database engine not running. All other services like reporting etc are running.

The server is set up to run under local system account. Logging in as administrator, .

This server is installed as default instance . ( I do have sql exp and sql server 200 dev edition installed as named instances)

Beginning to pull my hair out.

Any help would be greatly appreciated.

Regards,

Well, you said the database engine is NOT running? From the looks of things that's what you're trying to connect to...I'll assume a typo maybe? The DB Engine service must be running if you're trying to connect to the SQL engine...

|||

Thank you Chad for the illuminating response.

The problem is precisely that the database engine will not start , I understand that the engine must running order for me to connect to a database , however I have made no mention of trying to connect to a database.

If you have any helpful suggestions I would really appreciate it.

Thank you

Andy

|||

Hi Andy...honestly, everything you wrote in your initial posting was indicating that you were having trouble trying to connect to the server...per your initial post:

"I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine."

Then, the error message you posted indicates that you are indeed trying to connect to the server from an application:

"An error has occurred while establishing a connection to the server...."

And, it even describes a connection level provider (named pipes)...

So, given your original posting, it seems you are having trouble connecting to the instance, not getting it running. Myself and others would be more than happy to help you debug why you are having trouble getting the engine to start, but we'd need entirely different information.

If you'd like help with why the engine is not able to start, please post any error messages you notice in the application log, sql server error log, and system log related to the SQL Server instance, that's what we'd need to see to help you understand why the engine will not start.

On a final note, bear in mind that folks on the forums are trying to help you, not trying to insult you, and you'll always get more help if you treat myself and others with respect, not by being smart with us. You may notice that I am an administrator of these SQL forums, so please keep posts as civil as possible.

Regards

|||

HI Chad,

My apologies for coming across so curt , having re-read my response it does seem as though I was being rude , not my intention. Perhaps a bit of frustration creeping in, the problem is that my vocabulary and knowledge is lacking and expressing myself in a meaningful way is difficult and perhaps to some one with your knowledge, confusing.

If I am getting an error as described above when trying to get an instance started (i.e. the error is generated when I try and get the engine started) through Management Studio then I assume that error is relevant and that is what I will report on. Having read your second post it is now obvious that the error describes a connection problem rather than an issue regarding the instance running.( which obviously is as result of the engine not running.)

I checked the error log and found a network error which I googled , it seems as though if the via protocol is the culprit , having disabled this protocol the engine started .

The network error in the log:

TDSSNIClient initialization failed with error 0x7e, status code 0x60.

Thank you and my apologies once again.

|||

No worries, I definately understand frustation, we're all quite accustomed to that unfortunately. Glad you were able to get things working,

Regards,

sqlsql

Connectivity Issue with SQL Server 2005

Hi,
I have a SQL Server 2005 running on my machine with a named intance.
Recently I have got a DSL connection. After that the Microsoft SQL
Server Management Studio started giving connectivity issues.
Here I have copied the error Message. Could anybody help me out in
finding what is actually going wrong after getting a DSL Connection.
Thanks in Advance,
Suresh
TITLE: Connect to Server
--
Cannot connect to SURESH1023\SQLEXPRESS.
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an
error occurred during the login process. (provider: Named Pipes
Provider, error: 0 - The specified network name is no longer
available.) (Microsoft SQL Server, Error: 64)
For help, click:
http://go.microsoft.com/fwlink?Prod...64&LinkId=20476
BUTTONS:
OK
--"Gr8Ongole" <suresh.thotakura@.gmail.com> wrote in message
news:1165071352.266622.28580@.l12g2000cwl.googlegroups.com...
> Hi,
> I have a SQL Server 2005 running on my machine with a named intance.
> Recently I have got a DSL connection. After that the Microsoft SQL
> Server Management Studio started giving connectivity issues.
> Here I have copied the error Message. Could anybody help me out in
> finding what is actually going wrong after getting a DSL Connection.
> Thanks in Advance,
> Suresh
> TITLE: Connect to Server
> --
> Cannot connect to SURESH1023\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> A connection was successfully established with the server, but then an
> error occurred during the login process. (provider: Named Pipes
> Provider, error: 0 - The specified network name is no longer
> available.) (Microsoft SQL Server, Error: 64)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...64&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
Try forcing a TCP/IP connection by connecting to
tcp:SURESH1023\SQLEXPRESS
instead.
David

Connectivity Issue with SQL Server 2005

Hi,
I have a SQL Server 2005 running on my machine with a named intance.
Recently I have got a DSL connection. After that the Microsoft SQL
Server Management Studio started giving connectivity issues.
Here I have copied the error Message. Could anybody help me out in
finding what is actually going wrong after getting a DSL Connection.
Thanks in Advance,
Suresh
TITLE: Connect to Server
--
Cannot connect to SURESH1023\SQLEXPRESS.
--
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an
error occurred during the login process. (provider: Named Pipes
Provider, error: 0 - The specified network name is no longer
available.) (Microsoft SQL Server, Error: 64)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
--
BUTTONS:
OK
--"Gr8Ongole" <suresh.thotakura@.gmail.com> wrote in message
news:1165071352.266622.28580@.l12g2000cwl.googlegroups.com...
> Hi,
> I have a SQL Server 2005 running on my machine with a named intance.
> Recently I have got a DSL connection. After that the Microsoft SQL
> Server Management Studio started giving connectivity issues.
> Here I have copied the error Message. Could anybody help me out in
> finding what is actually going wrong after getting a DSL Connection.
> Thanks in Advance,
> Suresh
> TITLE: Connect to Server
> --
> Cannot connect to SURESH1023\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> A connection was successfully established with the server, but then an
> error occurred during the login process. (provider: Named Pipes
> Provider, error: 0 - The specified network name is no longer
> available.) (Microsoft SQL Server, Error: 64)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
Try forcing a TCP/IP connection by connecting to
tcp:SURESH1023\SQLEXPRESS
instead.
David

Connectivity Issue with SQL Server 2005

Hi,
I have a SQL Server 2005 running on my machine with a named intance.
Recently I have got a DSL connection. After that the Microsoft SQL
Server Management Studio started giving connectivity issues.
Here I have copied the error Message. Could anybody help me out in
finding what is actually going wrong after getting a DSL Connection.
Thanks in Advance,
Suresh
TITLE: Connect to Server
Cannot connect to SURESH1023\SQLEXPRESS.
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an
error occurred during the login process. (provider: Named Pipes
Provider, error: 0 - The specified network name is no longer
available.) (Microsoft SQL Server, Error: 64)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=64&LinkId=20476[/url]
BUTTONS:
OK
"Gr8Ongole" <suresh.thotakura@.gmail.com> wrote in message
news:1165071352.266622.28580@.l12g2000cwl.googlegro ups.com...
> Hi,
> I have a SQL Server 2005 running on my machine with a named intance.
> Recently I have got a DSL connection. After that the Microsoft SQL
> Server Management Studio started giving connectivity issues.
> Here I have copied the error Message. Could anybody help me out in
> finding what is actually going wrong after getting a DSL Connection.
> Thanks in Advance,
> Suresh
> TITLE: Connect to Server
> --
> Cannot connect to SURESH1023\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> A connection was successfully established with the server, but then an
> error occurred during the login process. (provider: Named Pipes
> Provider, error: 0 - The specified network name is no longer
> available.) (Microsoft SQL Server, Error: 64)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=64&LinkId=20476[/url]
> --
> BUTTONS:
> OK
> --
>
Try forcing a TCP/IP connection by connecting to
tcp:SURESH1023\SQLEXPRESS
instead.
David

Connections to SQL server are slow on one machine

Hi all,
My client PC is very slow to connect to all SQL server databases.
Other client machines are having no problem at all. I even tried
connecting to my local MSDE database, and the same behavior results.
If I try to connect via a .NET application it is also slow.

The connection is always made if I wait long enough, but then when I go
to query a table it is very slow again, even if I'm only returning one
row from a table with 5 fields.

Does anyone have any suggestions on how to troubleshoot this?

Thanks.check whether the ping time are different too ...
try switching off local firewall ...

"foreman_bob" <smhceh@.gmail.com> schrieb im Newsbeitrag
news:1137940934.406196.284270@.g47g2000cwa.googlegr oups.com...
> Hi all,
> My client PC is very slow to connect to all SQL server databases.
> Other client machines are having no problem at all. I even tried
> connecting to my local MSDE database, and the same behavior results.
> If I try to connect via a .NET application it is also slow.
> The connection is always made if I wait long enough, but then when I go
> to query a table it is very slow again, even if I'm only returning one
> row from a table with 5 fields.
> Does anyone have any suggestions on how to troubleshoot this?
> Thanks.|||What net library are you using? Is it the same net lib as the other
people that don't have issues? Are you authenticating the same way?Are
you requesting SSL or multiprotocol encryption from the client? Are
you located on the same LAN as the other users or do you dialup through
your 28KB modem into a VPN connection?

Greg|||I found out what was causing my problem today. I had ODBC tracing
turned on. As soon as I turned it off everything was fine.

Thanks for your replies.

Greg wrote:
> What net library are you using? Is it the same net lib as the other
> people that don't have issues? Are you authenticating the same way?Are
> you requesting SSL or multiprotocol encryption from the client? Are
> you located on the same LAN as the other users or do you dialup through
> your 28KB modem into a VPN connection?
> Greg|||wow.

Thank you! I am filing this one off!!!! I can totally see myself
turning it on, wandering off and forgetting it is on.

ick.

ConnectionOpen (PreLoginHandshake()). General Network Error

Hi all,
I'm getting the following error on my SQL on a local machine when running a
client program that connects to sql server located at the same machine. What
does it means? Do i have to configure in SQL settings?
[DBNETLIB]ConnectionOpen (PreLoginHandshake()). General Network Error.
thanks,
joelNormally this message would indicate a timeout of some kind attempting to
connect. Open the SQL Client Network Utility and see if Shared Memory is
enabled. If it is not enable it and see if the problem goes away. Local
connections by default should use shared memory so it would appear that
this is not enabled.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Connectiong to MSDE 2000

I installed MSDE 2000 on my machine running XP home
edition.
I can connect with all client utilities, include, query
analiser, enterprise manager, odbc, etc if i use the
builtin/administrator id, but i cant connect in the SQL
MODE.
If i set up an odbc connection for test, i get the
following error
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.
The ODBC error returns a state 28000 error, with is an
authenticaton error, please how can i correct thisMSDE is installed by default with Windows authentication, not with mixed
authentication, so you can't login with a SQL login, like 'sa'. You can
change this from Enterprise Manager by rightclicking the server, choosing
properties, and change the Authentication on the Security tab. You ahve to
restart SQL Server for the setting to take effect.
Jacco Schalkwijk
SQL Server MVP
"Lanre" <larry548997@.yahoo.com_anonymous> wrote in message
news:1b8701c3fc16$8a0ec650$a401280a@.phx.gbl...
> I installed MSDE 2000 on my machine running XP home
> edition.
> I can connect with all client utilities, include, query
> analiser, enterprise manager, odbc, etc if i use the
> builtin/administrator id, but i cant connect in the SQL
> MODE.
> If i set up an odbc connection for test, i get the
> following error
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user 'sa'. Reason: Not associated with a
> trusted SQL Server connection.
> The ODBC error returns a state 28000 error, with is an
> authenticaton error, please how can i correct this|||If you don't have Enterprise Manager, you can change the setting with the
steps from this article:
285097 INF: How to Change the Default Login Authentication Mode to SQL While
http://support.microsoft.com/?id=285097
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connectiong problem Sqlserver 2005 Express

I'm working with an Sqlserver 2005 Express database on my local machine, and using vs.net 2005.I need to enable the sqlserver cache by the way:

aspnet_regsql -E -d Northwind -ed

I encountered the remote connection problem(error:40).The northwind database was restored to the sqlserver 2005 express by the db file downloaded,and I added the ASPNET user.I also enabled the TCP/IP by using SQL Server Configuration Manager.

But all the web application connected to the Northwind database is working through the connection string:

"Data Source=WKS-DEV-04\SQLEXPRESS;Initial Catalog=Northwind;Integrated Security=True"

Any help will be much appreciated, thank you very much for reading my post

Can you telnet to the remote SQL Express service from the client? Using such command from commandline:

telnet xxx.xx.xx.xxx yyyy

Where Xs stand for ip address of the remote server, and Ys stand for TCP port of the service. You can check the TCP port of the SQL service in 'SQL Server Configuration Manager'->SQL Server 2005 Network Configuration

|||Thank you for your reply very much.I have got it done.

Connection works for a while then gets this : [DBMSLPCN]SQL Server does not exist or acces

Situation:
We have some custom code running on microsoft great plains **under
terminal services** on a windows 2003 machine.
We have a program (running under great plains) that will run for about
5 minutes, then give the error
[Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
or access denied.
I've tried disabling the shared memory protocol in the client network
utility. That didn't have any effect...even though the error points to
the shared memory protocol.
Now, I've got aql running on a non-standard port or 1150. If I change
this back to the default 1433, the program works fine.
Any ideas why?
Steven Vallarian
Hi
You may look at netstat to see what is connected to the ports of use PortQry
to see if you can connect:
http://support.microsoft.com/default...b;en-us;310099
It may be that you just have general network problems such as a faulty
switch.
John
"svallarian" <svallarian@.hotmail.com> wrote in message
news:1109778822.752029.318690@.l41g2000cwc.googlegr oups.com...
> Situation:
> We have some custom code running on microsoft great plains **under
> terminal services** on a windows 2003 machine.
> We have a program (running under great plains) that will run for about
> 5 minutes, then give the error
> [Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
> or access denied.
> I've tried disabling the shared memory protocol in the client network
> utility. That didn't have any effect...even though the error points to
> the shared memory protocol.
> Now, I've got aql running on a non-standard port or 1150. If I change
> this back to the default 1433, the program works fine.
> Any ideas why?
>
> Steven Vallarian
>

Connection works for a while then gets this : [DBMSLPCN]SQL Server does not exist or a

Situation:
We have some custom code running on microsoft great plains **under
terminal services** on a windows 2003 machine.
We have a program (running under great plains) that will run for about
5 minutes, then give the error
[Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does no
t exist
or access denied.
I've tried disabling the shared memory protocol in the client network
utility. That didn't have any effect...even though the error points to
the shared memory protocol.
Now, I've got aql running on a non-standard port or 1150. If I change
this back to the default 1433, the program works fine.
Any ideas why?
Steven VallarianHi
You may look at netstat to see what is connected to the ports of use PortQry
to see if you can connect:
http://support.microsoft.com/defaul...kb;en-us;310099
It may be that you just have general network problems such as a faulty
switch.
John
"svallarian" <svallarian@.hotmail.com> wrote in message
news:1109778822.752029.318690@.l41g2000cwc.googlegroups.com...
> Situation:
> We have some custom code running on microsoft great plains **under
> terminal services** on a windows 2003 machine.
> We have a program (running under great plains) that will run for about
> 5 minutes, then give the error
> [Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does
not exist
> or access denied.
> I've tried disabling the shared memory protocol in the client network
> utility. That didn't have any effect...even though the error points to
> the shared memory protocol.
> Now, I've got aql running on a non-standard port or 1150. If I change
> this back to the default 1433, the program works fine.
> Any ideas why?
>
> Steven Vallarian
>

Connection To Remote Server

I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
==================================================
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
==================================================
His server is set to allow remote connections. How do I resolve this?
Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999

> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>
|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.
|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.

Connection To Remote Server

I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
========================================
==========
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Serve
r
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
========================================
==========
His server is set to allow remote connections. How do I resolve this?Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999

> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422 How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.

Connection to database on a remote server

Here is my environment and problem:

I have VWD 2005 and SSE 2005 installed on my local machine. I also have these installed on my Windows 2003 Server. I developed my database using SSE on my local machine but pointing to directory on my server. I have been developing the web app using VWD on my server. I now want to use VWD on my local machine and point to the project on my server. I am able to open the project. In order to access the database in the "Database Explorer" I use as my "Data Source", "MS SQL Server (SQL Client) and it attaches fine and I can see my tables and data.

Now for my problem:

When I try to run the application "VIew in Browser", which login.aspx page is my first page, I get the page, but it doesn't inherit my master page which has the basic navigation and layout. Then after I try to login I get this message.

The file "W:\BBApp\App_Data\TimeTracker.mdf" is on a network path that is not supported for database files.
An attempt to attach an auto-named database for file W:\BBApp\App_Data\TimeTracker.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Here is a portion of my web.config file for the connection string.

<connectionStrings>

<removename="LocalSqlServer" />

<addname="LocalSqlServer"connectionString="Data Source=.\SQLExpress;Integrated Security=true;AttachDBFilename=|DataDirectory|TimeTracker.mdf;User Instance=true" />

My website I started with the source code for the TimeTracker start kit and have added more pages and changed the sitemap.

In general I guess I need to know how to handle using VWD on my local machine, but accessing the project on the server. The reason I'm doing this is because my colleague needs to be able to access the web app too to add pages to the site.

Thank you for any help.

Take a read of this articlehttp://www.aspspider.net/resources/Resource170.aspx
should see you right. Also if you are using membership remember you will need to take
care about the aspnetdb.mdf aswell.

Hope it help, if not let me know.

Connection to Analysis Server 9.0 option missing

I'm trying to connect to an OLAP cube on our SQL Server 2005 machine which is running Analysis Services (9.0). When I am trying to use the Crystal Reports menu in Visual Studio and selecting 'Crystal Reports', 'Database Expert', 'Create New Connection', 'OLAP', 'Add', the only Analysis Services option I get is for Microsoft OLE DB Provider for OLAP Services 8.0 which is SQL Server 2000. I cannot get the 9.0 provider to show.

HOWEVER: If I am in Crystal Reports itself and try to connect to Analysis Services 9.0, the option is there and I can connect. Note that if I try and then run this report from inside Visual Studio via Crystal Report Viewer, the report fails probably because it does not know where the 9.0 provider is....?

Microsoft Visual Studio 2005 Professional
Version 8.0.50727.762 (SP.050727-7600)

Crystal Reports XI Release 2 Developer Edition is also installed.

I've also installed a Crystal Reports patch form Business Objects called

'Crystal Reports XI Release 2

Support for MS SQL Server

2005 Analysis Services'

Any help?

I had this same problem, install the OLEDB 9.0 driver for analysis services on the server where BO lives:

http://www.microsoft.com/downloads/details.aspx?familyid=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&displaylang=en

That's only half the battle, you have to setup an spn for anaylsis services, trust things for delegation. You'll have to get a friendly domain admin to help. Here is a great white paper the BO support refered me to:

http://support.businessobjects.com/communityCS/TechnicalPapers/bo_voyager_xi_r2_configuring_msas_security.pdf

Connection to Analysis Server 9.0 option missing

I'm trying to connect to an OLAP cube on our SQL Server 2005 machine which is running Analysis Services (9.0). When I am trying to use the Crystal Reports menu in Visual Studio and selecting 'Crystal Reports', 'Database Expert', 'Create New Connection', 'OLAP', 'Add', the only Analysis Services option I get is for Microsoft OLE DB Provider for OLAP Services 8.0 which is SQL Server 2000. I cannot get the 9.0 provider to show.

HOWEVER: If I am in Crystal Reports itself and try to connect to Analysis Services 9.0, the option is there and I can connect. Note that if I try and then run this report from inside Visual Studio via Crystal Report Viewer, the report fails probably because it does not know where the 9.0 provider is....?

Microsoft Visual Studio 2005 Professional
Version 8.0.50727.762 (SP.050727-7600)

Crystal Reports XI Release 2 Developer Edition is also installed.

I've also installed a Crystal Reports patch form Business Objects called

'Crystal Reports XI Release 2

Support for MS SQL Server

2005 Analysis Services'

Any help?

I had this same problem, install the OLEDB 9.0 driver for analysis services on the server where BO lives:

http://www.microsoft.com/downloads/details.aspx?familyid=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&displaylang=en

That's only half the battle, you have to setup an spn for anaylsis services, trust things for delegation. You'll have to get a friendly domain admin to help. Here is a great white paper the BO support refered me to:

http://support.businessobjects.com/communityCS/TechnicalPapers/bo_voyager_xi_r2_configuring_msas_security.pdf

Connection Timeout

I am trying to upload data to my sql database via a web service installed on
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue to
get timeout error messages from my web service. I need my connection to stay
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgetting
some setting that still needs to be made?
Thanks,
Fred Herring
there is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>

Connection timeout

We recently moved our SQL Server to a faster machine. Everything is working great except every once in a while we get a connection timeout to the sql server. Everything else seems to be performing better but that initial connection is taking longer.

I realize this could be caused by a great deal of things, but if anybody has any suggestions I would appriciate it.

Thanks much.Leave an open connection for the next time the problem occurs. When it does, run exec sp_who2 and check the BlkBy column - if there is a value there, that is the id of the process (spid) that is blocking. Often you will have multiple blocking spids, and the key to that is to find the spid that is blocking at least one other spid but is not blocked - aka the culprit.

You can run DBCC INPUTBUFFER(culprit) to see what command it is running.

Happy hunting.

Connection Timeout

I am trying to upload data to my sql database via a web service installed on
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue t
o
get timeout error messages from my web service. I need my connection to sta
y
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgettin
g
some setting that still needs to be made?
Thanks,
Fred Herringthere is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>