Remote XML transfer

hello there,
I currently have a vb client application that outputs details to a well
formed xml document.
my question is, how can i send this information (automated) to my sql server
2005 ?
Im able to load the xml document locally, into a xml datatype and retrive it
fine, however the need is to complete this from a cleint machine across a
network.
I have looked for many examples but none seem to fit what im after.
any one help ?
regards
russ.
If you are using VB.NET then you can use ADO.NET to either insert the xml
into a table or pass the xml as a parameter to a stored procedure.
For an example of how this can be done in ADO.NET 2.0 see:
http://msdn.microsoft.com/data/DataA...sqlxml_ado.asp
Regards,
Galex Yen
"grumpy" wrote:

> hello there,
> I currently have a vb client application that outputs details to a well
> formed xml document.
> my question is, how can i send this information (automated) to my sql server
> 2005 ?
> Im able to load the xml document locally, into a xml datatype and retrive it
> fine, however the need is to complete this from a cleint machine across a
> network.
> I have looked for many examples but none seem to fit what im after.
> any one help ?
> regards
> russ.
>
>
>

Remote XML transfer

hello there,
I currently have a vb client application that outputs details to a well
formed xml document.
my question is, how can i send this information (automated) to my sql server
2005 ?
Im able to load the xml document locally, into a xml datatype and retrive it
fine, however the need is to complete this from a cleint machine across a
network.
I have looked for many examples but none seem to fit what im after.
any one help ?
regards
russ.If you are using VB.NET then you can use ADO.NET to either insert the xml
into a table or pass the xml as a parameter to a stored procedure.
For an example of how this can be done in ADO.NET 2.0 see:
http://msdn.microsoft.com/data/Data.../sqlxml_ado.asp
Regards,
Galex Yen
"grumpy" wrote:

> hello there,
> I currently have a vb client application that outputs details to a well
> formed xml document.
> my question is, how can i send this information (automated) to my sql serv
er
> 2005 ?
> Im able to load the xml document locally, into a xml datatype and retrive
it
> fine, however the need is to complete this from a cleint machine across a
> network.
> I have looked for many examples but none seem to fit what im after.
> any one help ?
> regards
> russ.
>
>
>

Remote SQL Server login failed for ASPNET user

This is a common problem, but none of the methods I read about in the other
posts have worked. What is a sure-fire way to get my web application to sto
p
using the ASPNET user for SQL Server authentication? I am trying to connect
to a Server on my LAN with a specified username and password. The error I
get is "Login failed for user '<computer name>\ASPNET'. I tried a standard
connection string and then one that Visual Studio generated when I dragged
the connection to a form:
"Server=<servername>;User ID=<userid>;Password=<password>Initial Catalog=<db
name>"
"workstation id=<my computer name>;packet size=4096;user
id=<user>;password=<password>;data source=<sql server name>;persist security
info=False;initial catalog=<db name>"
I have also tried putting in "Trusted_Connection=false". Also I saw
something about impersonation in the web.config, which i tried but it would
not compile.
The login works fine from inside the Visual Studio IDE and also through
Enterprise Manager.
Thanks for your help
SteveIn my experience this happens when you have the following conditions true...
1. You're using a connection string that's using Integrated Windows
authentication
2. Your web server is configured for anonymous access only
3. <identity impersonate="true" /> is set in your web config (system.web
section)
If your connection string uses a sql login:
User ID=<user>;password=<pwd>;Initial Catalog=<database>;Data Source=<server
>
You should never get this error if your using a SQL login, you're telling
the connection with what credentials to use to connect to the database, why
would it not use what you specified...? I'd double check the connection
string in the config file... You have to have "Integrated Security=True"
specified in your connect string otherwise you would not be attempting to
authenticate to the database using a windows account.
"Steve P" wrote:

> This is a common problem, but none of the methods I read about in the othe
r
> posts have worked. What is a sure-fire way to get my web application to s
top
> using the ASPNET user for SQL Server authentication? I am trying to conne
ct
> to a Server on my LAN with a specified username and password. The error I
> get is "Login failed for user '<computer name>\ASPNET'. I tried a standar
d
> connection string and then one that Visual Studio generated when I dragged
> the connection to a form:
> "Server=<servername>;User ID=<userid>;Password=<password>Initial Catalog=<
db
> name>"
> "workstation id=<my computer name>;packet size=4096;user
> id=<user>;password=<password>;data source=<sql server name>;persist securi
ty
> info=False;initial catalog=<db name>"
> I have also tried putting in "Trusted_Connection=false". Also I saw
> something about impersonation in the web.config, which i tried but it woul
d
> not compile.
> The login works fine from inside the Visual Studio IDE and also through
> Enterprise Manager.
> Thanks for your help
> Steve|||Thank you for responding, Alien2_51. I'll just go down your list:
1) I have made sure that my connection string does not include Integrated
Security=true"
2) I'm not sure about this. I'm just serving out the pages my my computer
(localhost). If I right-click on the default web site and go to directory
security, then to Edit anonymous access, the items that are checked are
"anonymous access", "allow IIS to control password", and "Integrated Windows
authentication". The user name in this dialog box is set to "IUSR_<my
computer name>". If I try to uncheck "integrated windows authentication", I
have to log in when I run the page and then the page won't even display.
3) In my machine.config file, impersonate="false". In the web.config of the
application, the value is not set.
Finally, I don't use the connection string that is in the web.config file
(sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes") I'm not
sure why it's in there; I just put the connection string in global.asax as a
n
application variable. I have also tried just hard-coding the connection
string into the code. I tried commenting out the connection string in
web.config to no avail.
Anyone please let me know if you have any other suggestions; your help is
certainly appreciated.
Thanks,
Steve
"Alien2_51" wrote:
> In my experience this happens when you have the following conditions true.
.
> 1. You're using a connection string that's using Integrated Windows
> authentication
> 2. Your web server is configured for anonymous access only
> 3. <identity impersonate="true" /> is set in your web config (system.w
eb
> section)
> If your connection string uses a sql login:
> User ID=<user>;password=<pwd>;Initial Catalog=<database>;Data Source=<serv
er>
> You should never get this error if your using a SQL login, you're telling
> the connection with what credentials to use to connect to the database, wh
y
> would it not use what you specified...? I'd double check the connection
> string in the config file... You have to have "Integrated Security=True"
> specified in your connect string otherwise you would not be attempting to
> authenticate to the database using a windows account.
>
>
>
> "Steve P" wrote:
>|||Figured out my problem...though the error message is misleading. Apparently
asp.net won't let you have 2 connections open at the same time (one to local
database and one to remote). I removed the local connection to test it and
it worked. Does anyone know how to have 2 simultaneous connections open? I
can use a dataset but the potential problem there is the amount of memory it
could use...
Thanks, Steve
"Steve P" wrote:

> This is a common problem, but none of the methods I read about in the othe
r
> posts have worked. What is a sure-fire way to get my web application to s
top
> using the ASPNET user for SQL Server authentication? I am trying to conne
ct
> to a Server on my LAN with a specified username and password. The error I
> get is "Login failed for user '<computer name>\ASPNET'. I tried a standar
d
> connection string and then one that Visual Studio generated when I dragged
> the connection to a form:
> "Server=<servername>;User ID=<userid>;Password=<password>Initial Catalog=<
db
> name>"
> "workstation id=<my computer name>;packet size=4096;user
> id=<user>;password=<password>;data source=<sql server name>;persist securi
ty
> info=False;initial catalog=<db name>"
> I have also tried putting in "Trusted_Connection=false". Also I saw
> something about impersonation in the web.config, which i tried but it woul
d
> not compile.
> The login works fine from inside the Visual Studio IDE and also through
> Enterprise Manager.
> Thanks for your help
> Steve|||Please disregard my last post. The error originated not from the remote
connection but from the local connection.
"Steve P" wrote:
> Figured out my problem...though the error message is misleading. Apparent
ly
> asp.net won't let you have 2 connections open at the same time (one to loc
al
> database and one to remote). I removed the local connection to test it an
d
> it worked. Does anyone know how to have 2 simultaneous connections open?
I
> can use a dataset but the potential problem there is the amount of memory
it
> could use...
> Thanks, Steve
> "Steve P" wrote:
>sql

remote sql server connection

Hi all,
I am trying to connect to remote sql server in vb.net application.
I am getting an error "login failed for user'abc' ".
why am I getting this error, what could be the possible reason.
any help will be appreciated.what is the login and password in your database?
whats ur connection string in vb.net?|||http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.

What is the connection string set and SQL server authentication?|||Originally posted by deidei76
what is the login and password in your database?
whats ur connection string in vb.net?

login: abc
password: abc

"data source=IP address of server;initial catalog=databasename;persist security info=False;user id=abc;workstation id=WSID;packet size=4096"|||Originally posted by Satya
http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.

What is the connection string set and SQL server authentication?
thanks satya.I am able to connect to the server now. simple and stupid mistake.I forgot to mention password in connection string.

Remote SQL Server

I've got a customer who has an application written in Access. They are
hitting some boundaries of Access, and are ready to move to SQL. They are
going to keep the front end in Access b/c of the massive amounts of code
they have written. We are going to set them up a SQL server in a datacenter,
and use linked tables in their access database. They have offices all over
the eastern half of the US, so they will need to connect to the SQL server
from anywhere, pretty much.
Basically my question is how can I keep this secure? I'm going to setup
encryption. Is it a bad idea to leave SQL server open on the public? How
can I lock it down and still keep functionality?I get about 10-20,000 hits a night from what looks like dictionary attacks.
Make sure all users & sa user have a a very long non standard password.
Can you lock the firewall down to a list of known host ranges on port 1433
?.
Run MS Base line security application on sql server box !.
Remove all non essensial db's on sql installation.
Regards
Don Grover
"Chris Miller" <cmiller@.compuville.net> wrote in message
news:1010agvq9v9k154@.corp.supernews.com...

quote:

---

> I've got a customer who has an application written in Access. They are
> hitting some boundaries of Access, and are ready to move to SQL. They are
> going to keep the front end in Access b/c of the massive amounts of code
> they have written. We are going to set them up a SQL server in a

---

datacenter,

quote:

---

> and use linked tables in their access database. They have offices all over
> the eastern half of the US, so they will need to connect to the SQL server
> from anywhere, pretty much.
>
> Basically my question is how can I keep this secure? I'm going to setup
> encryption. Is it a bad idea to leave SQL server open on the public? How
> can I lock it down and still keep functionality?
>

---

|||I'm going to try to lock it down to only a list of known host ranges, but
I'm not sure that will be possiable.
Where do I set what hosts each user can login from? Also, how do I set sa to
only be allowed to connect from localhost?
-Chris
"Don Grover" <spamfree@.assoft.com.au> wrote in message
news:%23JhsCNS4DHA.2404@.TK2MSFTNGP10.phx.gbl...

quote:

---

> I get about 10-20,000 hits a night from what looks like dictionary

---

attacks.

quote:

---

> Make sure all users & sa user have a a very long non standard password.
> Can you lock the firewall down to a list of known host ranges on port 1433
> ?.
> Run MS Base line security application on sql server box !.
> Remove all non essensial db's on sql installation.
> Regards
> Don Grover
> "Chris Miller" <cmiller@.compuville.net> wrote in message
> news:1010agvq9v9k154@.corp.supernews.com...
are[QUOTE]
> datacenter,
over[QUOTE]
server[QUOTE]
How[QUOTE]
>

---

|||Chris, I hope you don't mind if I piggyback my question onto yours;
We also have the need to make a sql database accessibly via internet. We
think our customers are going to demand encryption over the wire.
sql2k allows for ssl encryption at the protocol level, but my understanding
is that this would require our customers to enable ssl encryption on any sql
server they access from a given client. Am I wrong?
I recall seeing something about using the keyword "encrypt", either in the
connection string or in sql commands, but can find this nowhere in any dox.
Can anyone help me here?
So, what is the best way to do this?
Jeremy
"Chris Miller" <cmiller@.compuville.net> wrote in message
news:1010agvq9v9k154@.corp.supernews.com...

quote:

---

> I've got a customer who has an application written in Access. They are
> hitting some boundaries of Access, and are ready to move to SQL. They are
> going to keep the front end in Access b/c of the massive amounts of code
> they have written. We are going to set them up a SQL server in a

---

datacenter,

quote:

---

> and use linked tables in their access database. They have offices all over
> the eastern half of the US, so they will need to connect to the SQL server
> from anywhere, pretty much.
>
> Basically my question is how can I keep this secure? I'm going to setup
> encryption. Is it a bad idea to leave SQL server open on the public? How
> can I lock it down and still keep functionality?
>

---

|||I too will be using SLL Encryption via my ODBC connections.
-Chris
"Jeremy" <grand@.hevanet.com> wrote in message
news:%23NKtQwW4DHA.2136@.TK2MSFTNGP12.phx.gbl...

quote:

---

> Chris, I hope you don't mind if I piggyback my question onto yours;
> We also have the need to make a sql database accessibly via internet. We
> think our customers are going to demand encryption over the wire.
> sql2k allows for ssl encryption at the protocol level, but my

---

understanding

quote:

---

> is that this would require our customers to enable ssl encryption on any

---

sql

quote:

---

> server they access from a given client. Am I wrong?
> I recall seeing something about using the keyword "encrypt", either in the
> connection string or in sql commands, but can find this nowhere in any

---

dox.

quote:

---

> Can anyone help me here?
> So, what is the best way to do this?
> Jeremy
>
> "Chris Miller" <cmiller@.compuville.net> wrote in message
> news:1010agvq9v9k154@.corp.supernews.com...
are[QUOTE]
> datacenter,
over[QUOTE]
server[QUOTE]
How[QUOTE]
>

---

|||"Chris Miller" <cmiller@.compuville.net> wrote in
news:1010c2rc2c6kc99@.corp.supernews.com:

quote:

---

> I'm going to try to lock it down to only a list of known host ranges,
> but I'm not sure that will be possiable.
> Where do I set what hosts each user can login from? Also, how do I set
> sa to only be allowed to connect from localhost?

---

Did you find an answer to how you limit sa to localhost? I very like to
know this answer.
Masa|||By default there is no mechanism to do this. You could limit the machines
allowed to connect to the server via firewall or using Microsoft ISA server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin, are you saying there is no mechanism whatsoever, other than the
global ssl technique, to encrypt data over the wire? Not even a 3rd party
solution?
And yes, we can limit connections to known machines, but the market is
demanding encryption. What argument do we use to convince folks that
unencrypted transfers are ok?
Thanks, Jeremy

quote:

---

> By default there is no mechanism to do this. You could limit the machines
> allowed to connect to the server via firewall or using Microsoft ISA

---

server.

quote:

---

> Thanks,
> Kevin McDonnell
> Microsoft Corporation

---

|||My response was to a question regarding limiting the network interfaces.
I'm not sure what you meant by this reply:
"are you saying there is no mechanism whatsoever, other than the
global ssl technique, to encrypt data over the wire? Not even a 3rd party
solution?"
We can use SSL encryption with SQL 2000, which relies on PKI.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

remote server connection problems

Having all kinds of problems trying to establish a connection between a VB5 application and a remote server Sql Express database. The connection works fine with a user instance on my local machine. At one time I did have the remote connection working successfully using Sql Server authentication, whereby the application was passing the login and password through the connection string as so:

Provider=SQLNCLI.1;Persist Security Info=False;Data Source=<server name>\sqlexpress;Database=<database name>;Uid=<userid>;Pwd=<password>;

I've been away from using this development database for several weeks. Things are little foggy from that initial effort, and I recently tried putting up a newer copy of the development database on this server from my local machine copy. That local database copy apparently didn't have authentication login/user used by the app, so I created the Login account and assigned the default database, then created the User account, referenced it to the Login account, and gave the user account a role as db_owner. Now when my app attempts to connect with aforementioned connect string, I get an error "Login failed for '< userid>'. I've redone this thing a hundred times and I still get this error. I did put a Windows Update on this server recently so don't know if that's an issue.

I could try using Windows authentication mode, but am not sure how to establish Logins/Users under this mode. Mainly, I'm don't know what the name of these accounts should be. Do you set the Windows login name up in both Login and User accounts? Below is a modified connect string I'd probably use for this mode:

Provider=SQLNCLI.1;Persist Security Info=False;Integrated Security=SSPI;Data Source=<servername>\sqlexpress;Database=<database name>;

Any ideas or suggestion on things to try on either of these modes? At my wits on this and am up against the clock.

TIA ... Rick

If you're using SQL Authentication, the error would suggest that the UserID you're passing in your connection string either doesn't exist as a Login on the Server or that the Login does exist, but it isn't associated with a specific database User. You could probably find out the exact cause by looking in the error log, where it will list not only the error message, but the specific State. If you're getting the 18456 login error, the meaning of the common states can be found in this blog entry.

If you haven't read the Books Online topics covering security already, you should stop what your doing and go read them. No explaination provided in this forum is a subsitute for an actual understanding of the technology.

Regardless of the type of authentication you use, you need both a Login and a User in order to do anything in a database. The Login is what gives you access to the Server while the User is what gives you permission in the database. In Windows Auth, the Login is always associated with either a Machine or Domain User or Group, while SQL Auth Logins can just be any arbitrary name you want to give it. The Database user can be named pretty much anything you want to call it, you make the association between a Login and a User either using Management Studio UI or T-SQL commands. Here is a Windows Auth example:

Login - Domain\Rick (A Windows domain user)

Database User - Rick

You would associate the Domain\Rick Login with the Database User named 'Rick'. You would assign specific permissions in your database to the user named Rick, not to the Login. To be clear, I could have named the user Mike and it wouldn't make a difference. The Database User is totally separate from the Login and from the Windows Users in your domain. This is all explained in Books Online.

Mike

|||Hey Mike,

Mike Wachal - MSFT wrote:

If you're using SQL Authentication, the error would suggest that the UserID you're passing in your connection string either doesn't exist as a Login on the Server or that the Login does exist, but it isn't associated with a specific database User.

Neither of these is true. The Login account exist, default database selected as application database, password set, User account created that points to Login account of the same name, role given as db_owner. It should work. It does not.

You could probably find out the exact cause by looking in the error log, where it will list not only the error message, but the specific State. If you're getting the 18456 login error, the meaning of the common states can be found in this blog entry.[

It goes back and forth haphazardly between state 16 and state 8. Now it's consistently state 16 with a "cannot open database" error. What other permissions are there to give to this thing?

In another connectivity test, there was another oddity. Using Crystal Reports XI, I attempted to create a connection using OLE DB ADO. Selected "Provider for Sql Server" (note: couldn't get a connection out of their Sql Native Client option), logged into the database as SA. However, the application tables belonging to the database were not visible. Everything should be visble and available to SA, right?

Here's what I've been doing to move a copy of the local database up to a development test server, using SqlExpress Manager:

- Detach local db
- Detatch server db and deleted existing MDF/LDF pair since I'm going to overwrite these.
- Copy MDF/LDF pair up to server
- Attach pair to server
- Rename database, removing full pathname from database name.
- Create Login account used by app as Sql Server authentication and establish default db for app. Note, this login seems to persist each time I perform this sequence. Doesn't seem to make a difference if I use what's there, or delete it and start fresh.
- Create User account of same name and point Login Account. Assign role as db_owner.
- Reattach app database on local machine to it's available there again.

This should work, and I had it working once before. Windows authentication mode isn't allowing a connection either. As it is, I've spent a few days on this, am frustrated, and about ready to give up on SqlExpress and move on MySql.

Supplement: I just uninstalled and reinstalled SqlExpress and Sql Native Client on the server. I didn't remove any of the extra tools and such. After successful installation I was going to reconfigure for remote access, however, all my settings were still configure for remote access. I restarted the service(s), including Sql Browser. Ran the process of moving a copy of the database over to server (again), attached, and ... same old error ... "cannot open database", both with Sql and Windows authentication.

Rick

|||Mike,

Well, after three days of troubleshooting, the problem turned out to be that the database name in the connection string must explicitly reference the .MDF extension. For example...

Problematic connect string:
connection=Provider=SQLNCLI.1;Persist Security Info=False;Data Source=<server name>\sqlexpress;Database=myDatabase

Working connection string

connection=Provider=SQLNCLI.1;Persist Security Info=False;Data Source=<server name>\sqlexpress;Database=myDatabase.mdf

To the best of my recollection, Sql Server doesn't normally require an extension, but apparently Sql Express now does.

Rick|||

SQL Express does not require the extention, but it does require the correct name. SQL Server will also keep a hold of the name of a database and tie it to a specific file location, even after detach. Database names can be pretty much anything, including a full path to a file, in fact, when you use AttachDbFilename and don't specificy an explicit name, your database will actually be given an "auto name" that is the path to the file.

It appears that at some point in the past, the file managed to get named as the file name with extenstion rather than just the base file without extention. Since that informaiton is cached in some form in the Master database, the next time you attached a database from the same path, it "picks up" to name from the previous attach. This isn't unique to SQL Express, any copy of SQL Server could do this.

If you look in Management Studio at the server, you should find the database name listed as myDatabase.mdf. You should be able to change this if you want by just renaming the database.

Mike

|||Yeah, I thought about it some more overnight. When moving the local copy up to server and renaming the file (removing the full path from the name), I didn't remove the .MDF extension. So, just have to be mindful of this in future when attaching any database to the server.

remote message being classified as local

Hi

I am trying to deploy our service broker application into our live enviroment. I have been using the excellent service listings manager to configure security and routes when deploying to our test enviroments and had no problems. However, after having gone through the same steps in live, i can not get it working.

The messages I try sending from the remote initiating service arrives at the target service, but the ack is not sent back from the target service. I have used profiler to find out what is going on and noticed that on the target after the ack is received, a broker:message classify event occurs with an event sub class of 1 - Local. It then starts going through lots of broker: Message undeliverable events. From what I understand this means that the target service has classified that the reply to the message should be sent to a local service instead of a remote service which is not the case.

I think the remote route is set up correctly on the target server. I have run this query on the target server after one message has been sent

select r.*

from sys.conversation_endpoints e

inner join sys.routes r on e.far_service = r.remote_service_name and e.far_broker_instance = r.broker_instance

and it returns the row from sys.routes that points to the initiating service.

Can anybody help with what else I can do to solve this problem?

Antony

something very strange was going on in my server.

A few days after this happened, all messages stopped being sent on the target server (even local ones between databases on the server)

I restarted sql server and everything started working - the remote messages started being classified as remote again and were sent correctly back to the initiating service.

I guess somehow service broker had got corrupted in this instance, though there were no dumps or error messages about this.

|||

Can you send the ERRORLOG from the time it run with the problem to remus.rusanu@.microsoft.com ?

Thanks,
~ Remus

|||

anthony_brown wrote:

The messages I try sending from the remote initiating service arrives at the target service, but the ack is not sent back from the target service. I have used profiler to find out what is going on and noticed that on the target after the ack is received, a broker:message classify event occurs with an event sub class of 1 - Local. It then starts going through lots of broker: Message undeliverable events. From what I understand this means that the target service has classified that the reply to the message should be sent to a local service instead of a remote service which is not the case.

One thing to keep in mind is that incomming message from the wire are normally actually classified 'LOCAL'. The process is described in BOL: http://msdn2.microsoft.com/en-us/library/ms166052.aspx When an incomming message arrives on an instance, it is classified in the MSDB database to find the destination service. Typically the AutoCreatedLocal route in msdb.sys.routes will expose all services on every database in the instance to the incomming message. As such, the result of this classification will be '1 - Local' but the DatabaseId of the event will be '4' (msdb). This is the correct and expected behavior of a typical deployment.

HTH,
~ Remus

Remote Deployment

I have developed and tested few reports using SQL Server 2000 Reproting
Service.
Now I want to deploy it with my Web Application Setup. Please advice
how can I do
that. I don't have access to remote server as it is on their local
intranet. Client simply
don't want us to access their machines. Is there any solution?
Thank you,
Best Regards
Tanweer BadamiYou can use Reporting Services Scripter to generate deployment scripts. You
can then supply them as is, or modify the batch file so you can pass in the
Report Server name as part of your setup (or simply use them as a basis for
your own deployment scripts)
Download Reporting Services Scripter
http://www.sqldbatips.com/showarticle.asp?ID=62
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Robert" <trbadami@.gmail.com> wrote in message
news:1137481899.124207.258680@.g43g2000cwa.googlegroups.com...
>I have developed and tested few reports using SQL Server 2000 Reproting
> Service.
> Now I want to deploy it with my Web Application Setup. Please advice
> how can I do
> that. I don't have access to remote server as it is on their local
> intranet. Client simply
> don't want us to access their machines. Is there any solution?
> Thank you,
> Best Regards
> Tanweer Badami
>|||Thanks alot Smith, I will try that and get back to you asap.
Best Regards
Tanweer Badami|||wow, I deployed it successfully. Reporting Service Scripter is a great
utility.
Thank a lot Smith.
Best Regards
Tanweer Badami|||HI I find difficulty in deploying
I have to pass the password name after running scripts.
"Robert" wrote:
> wow, I deployed it successfully. Reporting Service Scripter is a great
> utility.
> Thank a lot Smith.
> Best Regards
> Tanweer Badami
>

Remote DB - best practices?

We have an application requirement that calls for a local running Windows
Froms application that will need to be connected to a central database over
the internet. Data volumes will be small but latency is a concern. My
first thought is to simply have a connectionstring to the remote db.
Another thought is to connect via web services. I'm thinking that WCF or
Remoting would be too much work.
Anyway, what is the best way? From a development standpoint? From an
operational durability standpoint?
Thanks,
TI think querying your databases using stored procedures via web services is
a good and secure way.
--
Ekrem Önsoy
"Tina" <TinaMSeaburn@.nospamexcite.com> wrote in message
news:exL3RCRBIHA.4836@.TK2MSFTNGP06.phx.gbl...
> We have an application requirement that calls for a local running Windows
> Froms application that will need to be connected to a central database
> over the internet. Data volumes will be small but latency is a concern.
> My first thought is to simply have a connectionstring to the remote db.
> Another thought is to connect via web services. I'm thinking that WCF or
> Remoting would be too much work.
> Anyway, what is the best way? From a development standpoint? From an
> operational durability standpoint?
> Thanks,
> T
>

Remote Database Deployment

We have an application using a SQL 2005 database which we need to deploy to a client. The only we can find of deploying the structure and the data is to perform a backup on the source server and a restore on the destination server.

Is this really the best/only way to deploy a database? I'd appreciate any pointers.

Thanks in advance

LazyGenius wrote:

We have an application using a SQL 2005 database which we need to deploy to a client. The only we can find of deploying the structure and the data is to perform a backup on the source server and a restore on the destination server.

Is this really the best/only way to deploy a database? I'd appreciate any pointers.

Thanks in advance

If you're using SQL 2005 you don't even need to backup/restore. You can just Xcopy your mdf (and optionally ldf) files and do an attach.

|||

It all seems a bit "DOS" to me but thanks for the quick reply. We have a small utility program to attach the database so I guess we'll just use that.

Thanks again

|||

Hey you asked for a better way of doing it. Think of the time that it would take to backup and restore a large database. Compare that with detaching it, making a copy, and attaching that copy on the other end.

Remote database Connection Error!

Hi,
My Application which is written in VB.Net uses database connection to my
Local Instance of SQL Server Express version.
My connection string is " Data
Source=SM5\SQLEXPRESS;AttachDbFilename=C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial Catalog=MgmtSystem;Persist
Security Info=True;User ID=sa;Password=belmont". When I run my application
from the same machine where SQL Server instance is installed, it works fine.
But now I am intending to use it as Client-Server type as database on Server
and application running from another machine. To test this I have deployed
my application on another machine. When I run it I get following error, "An
error has occured 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 setting SQL Server does not allow remote
connections.(provider: SQL Network Interface, error: 26 - Error Locating
Server/Instance specified)(Microsoft SQL Server Error:-1).
To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
Pipe). Then I even started SQL Browser service to enable the instance to be
browsed by client. Then Checked if Hide Instance property. Still no Luck.
I am really going crazy. This is really important for me since we are
migrating from Access to SQL Server Express. Since in Access my application
can have client server
Architecture. Same thing I need to have in SQL Express.
Any help is really appreciated.
Thanks,
Sujatause sql2k5 surface area configuration tool to enable 'remote connections'.
--
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured 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 setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> Sujata|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:
> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> > Hi,
> > My Application which is written in VB.Net uses database connection to my
> > Local Instance of SQL Server Express version.
> > My connection string is " Data
> > Source=SM5\SQLEXPRESS;AttachDbFilename=C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> > Catalog=MgmtSystem;Persist
> > Security Info=True;User ID=sa;Password=belmont". When I run my application
> > from the same machine where SQL Server instance is installed, it works
> > fine.
> > But now I am intending to use it as Client-Server type as database on
> > Server
> > and application running from another machine. To test this I have
> > deployed
> > my application on another machine. When I run it I get following error,
> > "An
> > error has occured 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 setting SQL Server does not allow remote
> > connections.(provider: SQL Network Interface, error: 26 - Error Locating
> > Server/Instance specified)(Microsoft SQL Server Error:-1).
> >
> > To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> > Pipe). Then I even started SQL Browser service to enable the instance to
> > be
> > browsed by client. Then Checked if Hide Instance property. Still no Luck.
> > I am really going crazy. This is really important for me since we are
> > migrating from Access to SQL Server Express. Since in Access my
> > application
> > can have client server
> > Architecture. Same thing I need to have in SQL Express.
> >
> > Any help is really appreciated.
> >
> > Thanks,
> > Sujata
>
>

remote database connection

Hello,

My database stays in a remote site and I have access it through VPN. I would like connect my current Windows based Asp.Net application with this database. What are my options? Can I connect remote database with SqlDataAdaper, will that be slow? Should I sue Web Services to connect database?

If you can Ping the database server from the server running the ASP.NET code, you should be able to connect the exact same way as you can connect to a machine right next to your machine. The speed or slowness depends upon exactly what you are doing. It is likely that using the standard SqlClient classes will be faster and easier than trying to do it using a Web Service.

Remote database access

Hi can anybody know how to connect remote database with asp.net application? Actually my database is in different machine (in different server, different location) so i want to connect that server. Every time I'm getting the fallowing message

An error has occured 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.

Thank you,

Nagu

Hi,

Please check the article athttp://www.kodyaz.com/content/SQLServerdoesnotallowremoteconnections.aspx about this default security configuration and altering this setting

You can use the Surface Area Configuration tool in order to let remote connections.

Eralper

|||

Hi nagsline ,

First of all enable mixed mode authentication for accessing the database. If you are using an sql username and password make sure that user have access to your database.

|||Also make sure your connection string is correct ie. you have mentioned the correct system name or Ip address etc.|||I don't know if this helps but I thought I would point out that you receive this exact error also when your SQL server is stopped and you try connecting to it.

Remote Connections Refused when server under load

Hi All,
We have a .NET 2.0 web application. Occasionally, we get the following
error below when we are doing performance testing. It is not consistent and
only happens every once in awhile. We are using TCP/IP and only have one
instance of SQL running. We do specify connection pooling in the connection
string. There is virtually nothing happening on the database server - it
only contains a few rows of data to control navigation for the site.
System.Data.SqlClient.SqlException: 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
This is a different error and not quite what you describe but it might be
involved in your problem. This is from the Books Online topic "Server
Network Configuration."
Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
When testing scalability with a large number of client connection attempts
to an instance of the SQL Server Database Engine running on Windows Server
2003 Service Pack 1, Windows may drop connections if the requests arrive
faster than SQL Server can service them. This is a security feature of
Windows Server 2003 Service Pack 1, which implements a finite queue for
incoming TCP connection requests. It results in the following error:
ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
connection was forcibly closed by the remote host ...
To resolve this issue, use the regedit.exe utility to add the following
registry key:
Key Type Name Value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\
DWORD
SynAttackProtect
00000000
Security Note:
Setting this registry key may expose the server to a SYN flood,
denial-of-service attack. Add this registry value only if necessary and with
an understanding of the security risks. Remove this registry value when
testing is complete.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bill P" <Bill P@.discussions.microsoft.com> wrote in message
news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
> Hi All,
> We have a .NET 2.0 web application. Occasionally, we get the following
> error below when we are doing performance testing. It is not consistent
> and
> only happens every once in awhile. We are using TCP/IP and only have one
> instance of SQL running. We do specify connection pooling in the
> connection
> string. There is virtually nothing happening on the database server - it
> only contains a few rows of data to control navigation for the site.
> System.Data.SqlClient.SqlException: 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
|||Rick,
Thank you for the reply. It very well could have something to do with this.
I am going to give it a try. It may be a few days before I find anything
out since this happens only once in a while.
Bill Portman
"Rick Byham, (MSFT)" wrote:

> This is a different error and not quite what you describe but it might be
> involved in your problem. This is from the Books Online topic "Server
> Network Configuration."
> Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
> When testing scalability with a large number of client connection attempts
> to an instance of the SQL Server Database Engine running on Windows Server
> 2003 Service Pack 1, Windows may drop connections if the requests arrive
> faster than SQL Server can service them. This is a security feature of
> Windows Server 2003 Service Pack 1, which implements a finite queue for
> incoming TCP connection requests. It results in the following error:
> ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
> connection was forcibly closed by the remote host ...
> To resolve this issue, use the regedit.exe utility to add the following
> registry key:
> Key Type Name Value
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\
> DWORD
> SynAttackProtect
> 00000000
> Security Note:
> Setting this registry key may expose the server to a SYN flood,
> denial-of-service attack. Add this registry value only if necessary and with
> an understanding of the security risks. Remove this registry value when
> testing is complete.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bill P" <Bill P@.discussions.microsoft.com> wrote in message
> news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
>

Remote Connections Refused when server under load

Hi All,
We have a .NET 2.0 web application. Occasionally, we get the following
error below when we are doing performance testing. It is not consistent and
only happens every once in awhile. We are using TCP/IP and only have one
instance of SQL running. We do specify connection pooling in the connection
string. There is virtually nothing happening on the database server - it
only contains a few rows of data to control navigation for the site.
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. When connecting to SQL Server 2005, this failur
e
may be caused by the fact that under the default settings SQL Server does no
t
allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL ServerThis is a different error and not quite what you describe but it might be
involved in your problem. This is from the Books Online topic "Server
Network Configuration."
Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
When testing scalability with a large number of client connection attempts
to an instance of the SQL Server Database Engine running on Windows Server
2003 Service Pack 1, Windows may drop connections if the requests arrive
faster than SQL Server can service them. This is a security feature of
Windows Server 2003 Service Pack 1, which implements a finite queue for
incoming TCP connection requests. It results in the following error:
ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
connection was forcibly closed by the remote host ...
To resolve this issue, use the regedit.exe utility to add the following
registry key:
Key Type Name Value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\Tcpip\Parameters\
DWORD
SynAttackProtect
00000000
Security Note:
Setting this registry key may expose the server to a SYN flood,
denial-of-service attack. Add this registry value only if necessary and with
an understanding of the security risks. Remove this registry value when
testing is complete.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bill P" <Bill P@.discussions.microsoft.com> wrote in message
news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
> Hi All,
> We have a .NET 2.0 web application. Occasionally, we get the following
> error below when we are doing performance testing. It is not consistent
> and
> only happens every once in awhile. We are using TCP/IP and only have one
> instance of SQL running. We do specify connection pooling in the
> connection
> string. There is virtually nothing happening on the database server - it
> only contains a few rows of data to control navigation for the site.
> System.Data.SqlClient.SqlException: 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|||Rick,
Thank you for the reply. It very well could have something to do with this.
I am going to give it a try. It may be a few days before I find anything
out since this happens only once in a while.
Bill Portman
"Rick Byham, (MSFT)" wrote:

> This is a different error and not quite what you describe but it might be
> involved in your problem. This is from the Books Online topic "Server
> Network Configuration."
> Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
> When testing scalability with a large number of client connection attempts
> to an instance of the SQL Server Database Engine running on Windows Server
> 2003 Service Pack 1, Windows may drop connections if the requests arrive
> faster than SQL Server can service them. This is a security feature of
> Windows Server 2003 Service Pack 1, which implements a finite queue for
> incoming TCP connection requests. It results in the following error:
> ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
> connection was forcibly closed by the remote host ...
> To resolve this issue, use the regedit.exe utility to add the following
> registry key:
> Key Type Name Value
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\Tcpip\Parameters\
> DWORD
> SynAttackProtect
> 00000000
> Security Note:
> Setting this registry key may expose the server to a SYN flood,
> denial-of-service attack. Add this registry value only if necessary and wi
th
> an understanding of the security risks. Remove this registry value when
> testing is complete.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Bill P" <Bill P@.discussions.microsoft.com> wrote in message
> news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
>

Remote connection to SqlServer

Hello Guys
We are developing a CRM application using Delphi Front end &
Sqlserver as back end which is
residing on Windows 2000 server. I need a best possible solution,
if this CRM app fornt end is installed in different Location and
making connection to the Sqlserver which is altogether in different site...
Thanks
Chandru
There is usually no problem at all using the OLEDB SQL-Server driver over
the internet if the port 1433 is not blocked by a firewall or if you are
able to setup a proxy server. The transport layer will be totally
transparent to your application.
S. L.
"Chandru" <chandru@.knigthoodcorporate.com> wrote in message
news:%23OnHId0xEHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hello Guys
> We are developing a CRM application using Delphi Front end &
> Sqlserver as back end which is
> residing on Windows 2000 server. I need a best possible solution,
> if this CRM app fornt end is installed in different Location and
> making connection to the Sqlserver which is altogether in different
> site...
>
> Thanks
> Chandru
>
>
>

Remote connection to SqlServer

Hello Guys
We are developing a CRM application using Delphi Front end &
Sqlserver as back end which is
residing on Windows 2000 server. I need a best possible solution,
if this CRM app fornt end is installed in different Location and
making connection to the Sqlserver which is altogether in different site...
Thanks
ChandruThere is usually no problem at all using the OLEDB SQL-Server driver over
the internet if the port 1433 is not blocked by a firewall or if you are
able to setup a proxy server. The transport layer will be totally
transparent to your application.
S. L.
"Chandru" <chandru@.knigthoodcorporate.com> wrote in message
news:%23OnHId0xEHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hello Guys
> We are developing a CRM application using Delphi Front end &
> Sqlserver as back end which is
> residing on Windows 2000 server. I need a best possible solution,
> if this CRM app fornt end is installed in different Location and
> making connection to the Sqlserver which is altogether in different
> site...
>
> Thanks
> Chandru
>
>
>

Remote connection to database on same PC?

I am running the SQL express advanced on the same PC that also hosts my Visual Basic Express application. I have user instances turned off and full-text enabled and working from within a SQL query window. However, I can not create a working connection to the database using the data source wizard from the server explorer within VB.NET. Since this is on the same PC, do I need to enable anything other than shared memory? I get the error: Provider SQL Network Interfaces, error 26 Error locating server/instance.

DeBug

hi DeBug,

if you are using VBExpress, I've heard the data source wizard should not be able to use connections other than user instances.. you should modify the connection context in your code, pointing to the "shared" SQLExpress data source..

personally I'm not able to help more, as I only own the full VS edition..

regards

|||

Hi,

when you say you turned user instances off, do you mean that you installed the default instance and not a named instance?

What Data source, Servername and log on type did you choose when you tried to add the SQL server to the server explorer?

Are you running VB.Net in the same windows account you installed SQL Express with?

--
SvenC

|||

I believe that user instances are disabled for use with full-text search so I set the User Instance to False. The following connection string both fail:

Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\SGExpress.mdf";Integrated Security=True;Connect Timeout=30;User Instance=False

Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\SGExpress.mdf";Integrated Security=True;Connect Timeout=30;User Instance=False

I installed VB and SQL Express using my administrative user account logged on locally to the PC. I'm am not being logged into any domain server but only to the local PC.

DeBug

|||

Update: I can connect to the database using the following code in a VB.NET application but not with the Data Source Configuration Wizard. The wizard will not allow me to enter ".\" where it assigns the ".\SQLExpress" and other instances.

Dim conn As New SqlConnection()

conn.ConnectionString = "Data Source=.\;Initial Catalog=SGExpress;Integrated Security=True;Integrated Security=True"

conn.Open()

Me.Text = conn.ServerVersion

conn.Close()

The Microsoft SQL Server Reporting Service wizard allows me to produce and connect the following xml DataSource.rds file:

<?xml version="1.0" encoding="utf-8"?>
<RptDataSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>DataSourcePlats</Name>
<DataSourceID>cf8ea427-70f2-4a10-8989-61ed5f9bd74c</DataSourceID>
<ConnectionProperties>
<Extension>SQL</Extension>
<ConnectString>Data Source=.\;Initial Catalog=SGExpress</ConnectString>
<IntegratedSecurity>true</IntegratedSecurity>
</ConnectionProperties>
</RptDataSource>

However, even though I saved the above data source as Shared, it does not show up in VB.NET.

How can I manually create a DataSource for my Visual Basic Express applications? I believe this problem is related to the fact that my SQL Express was installed to allow for full-text indexing and does not have indivual instances.

DeBug

|||

Did you try to use only . instead of .\

You might also try your real computer name.

How did you install SQL Server? Did you specify an instance name? Did you install more than one instance? What services do you see in service manager (Start->Run : services.msc) which start with "SQL Server". Please post the exact names.

--
SvenC

|||

The wizard will only let me select an instance from the drop down box. I can not edit that property to key in: ".", " .\", or my computer name.

I installed SQL Server Express Advanced using the EXE downloaded from the MSDN web site. It created a directory like "C:\d3705b3534f0937859a" and installs from there. I do not recall specifing a instance name on the last intall as per the full-text requirements. I have however used the SQL Express (not advanced) with an instance name on this PC. That version of SQL Express was removed using the ADD/Remove and the newer SQL Express with full-text search was then installed.

Service Manager:

SQL Server FullText Search (SQLEXPRESS) - stopped, auto

SQL Server (MSSQLSERVER) - started, auto

SQL Server Active Directory Helper - stopped, disabled

SQL Server Browser - started, auto

SQL Server FullText Search (MSSQLSERVER) -started, auto

SQL Server VSS Writer - stopped, manual

I can connect using ADO.NET in Visual Basic Express using just code but fail at creating a data connection via the wizard.

DeBug

|||

Hmm, the way you use the server explorer in VB.Net Express seems to be different to the full version of Visual Studio 2005 I use. In the server explorer I see a top node "Data Connections" where I can right click to add a connection. In the following dialog I can enter the computer name where SQL server is running. The data source field is a bit misleading as I can only choose which provider to use. I have a few screenshots how it looks on my machine:

http://i112.photobucket.com/albums/n193/Sven_Carstensen/vs_Server1.gif

http://i112.photobucket.com/albums/n193/Sven_Carstensen/vs_Server2.gif

http://i112.photobucket.com/albums/n193/Sven_Carstensen/vs_Server3.gif

Is that comparable to your server explorer UI? Otherwise I hope someone with VB.Net Express can help.

--
SvenC

|||

Visual Basic Express has a "Database Explorer" which contains a collection of Data Connections. I can right click the Database Explorer pane and choose Add Connection. This launches the Add Connection wizard which allows me to select the data provider, the database file, and other connection parameters. When I click the Test Connection button, it always fails. However, if I code a connection with ADO.NET as noted in my previous posts, I can in fact connect and display a query in a DataGridView control. I've used the wizard in the past to create connections and I'm puzzled why it is failing now. The only thing I changed when removing and then reinstalling SQL Express with Advanced Services, is installing using the default instance and disabling user instances as per the full-text documentation. If I right click in the code window of Visual Basic Express and insert the snippet "create a local SQL connection to SQL Express" it also fails with what I think should be a correct connection string. If I insert the snippet "create a server based connection SQL Server" then it works correctly. I think the wizard is trying to create the same type as the local SQL connection to SQL Express and fails for the same reason. I'm struggling to discover that reason.

DeBug

|||

That sounds like a limitiation in the Express edition of VB. The database explorer seems to always expect the named instance SQLExpress which you now no longer have.

You might need to use SQL Server Management Studio Express instead of the build in Database Explorer to manage your SQL server. That should give you full control to what server and instance you want to connect.

Maybe some Microsoft person has better details about using the Database Explorer with other instance names as SQLExpress?

--
SvenC

|||

Hi Doug,

Andrea is right, VB Express uses User Instances by default, although I would have expected a different error that your getting.

If you're trying to create a database directly in your project (i.e. Right-click in the project folder and use the Add New Item | Database functionality) you will have to use User Instance, that's the only way it works.

If you've already created a database on the parent instance of your server, then you can make a connection to it in the Database Manager, but you'll need to go into the Advanced properties and change User Instance to false. You will have to point at the actual database file, even though it is already attached, because that's just the way VB Express is designed to work. (In short, both VB Express and C# Express were designed with the assumption that they would be used only to create single user applications with data stored locally by using User Instances. Because of this, the connections work in a specific way.)

Another possibility given the error, is that you've installed your Instance of SQL Express to a non-default Instance Name. (something other than SQLEXPRESS) If that is the case, you'll need to modify the properties of your VB Express installation to use your Instance Name. By default, VB Express is configured to use SQLEXPRESS as the Name Instance. You can do this on the Tools | Properties menus. Select the check box to show all properties in the dialog and then look in the Data properties.

Mike

Remote connection to Analysis Service giving problem.

Hi,

I am stuck up with one of the deployment scenario. I have web application through which we can invoke reports. Reports are developed in SQL Server 2005 Reporting Service.

The reporting service project sets data source connection with Analysis Services database.

If we have all this on the same machine, we are able to integrate and see the results end to end.

However we are stuck up with the following deployment scenario.

Say our web application is on A machine
SQL Server 2005 database on B machine
SQL Server 2005 Analysis Services on C machine
SQL Server 2005 Reporting Services on D machine.

so analysis services C machine pointing to database on B machine. and reporting services D machine pointing to analysis services C machine.

So in Reporting Service project when we set the data source connection to a remote Analysis services machine (C)
it gives us the following error that "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running."

Is this a known issue? I searched on google and this forum but dint get much help. I did check that for analysis service remote connection is enabled.

What exact steps do I have to follow?

First of all is this scenario ok that analysis services and reporting services on different machine?

This is very urgent for our project. Please help me find the solution.

Thanks in advance!

Note: I have posted a similar post in Reporting Services forum.

Ann.

This problem relates to the fact that two separate servers cannot identity a user without that you use Kerberos for authentication. If you have a network with Active Directory it is configuration issue. This feature is already in place.

Search on Windows 2003, Active Directory and Kerberos.

Mosha have a post on this regarding SSAS2005 here:

http://www.mosha.com/msolap/articles/kerberos_delegation.htm

HTH

Thomas Ivarsson

Remote connection Problem With SQL 2005 Thru VB Application

Hi guys,

Any one is there to help me?

I have problem remotely connecting SQL 2005 thru my VB Aplication.

I have set up a SQL Server 2005 to use for testing before moving to another production server.

I have set it to to allow remote connections and use TCP IP only and have opened TCP port 1433 on the Windows XP firewall and am using the SQL Sever on Port UDP 3544 Also the Server Browser service is running. The server is connected directly to the internet on a static IP (eg. 10.0.0.3)

When I try to connect to the database on another computer it fails.

Thanks for any insight

RiyazHi Riyaz,

Can you clarify - the remote server is remote ? Do you mean outside your Lan ie on the internet ? Or do you mean remote - not running on your local machine ie localhost ?

Regards Purple|||

Quote:

Originally Posted by Purple

Hi Riyaz,

Can you clarify - the remote server is remote ? Do you mean outside your Lan ie on the internet ? Or do you mean remote - not running on your local machine ie localhost ?

Regards Purple

Dear Purple,

My Server Name is "Server" I need connect Via Internet, out side Lan remotely also would like to connect Lan as well.

Previously I am using SQL 2000 I used following connection string to connect database inside Lan.

OpenConnection = Ado_Open(MSSQLConnString("Server", "xxx", "xxx", "xxxxx"))

Best regards,
Riyaz|||Can you connect to the database when you are inside the Lan or have you no connection to the database server at all ?

Purple|||

Quote:

Originally Posted by Purple

Can you connect to the database when you are inside the Lan or have you no connection to the database server at all ?

Purple

Hi Parple,

Not yet my first SQL Server 2005 connection i am trying to establish via internet. Also I would like to know connect Lan.

Thanks!

Regards,
Riyaz|||Hi,

Could I suggest you try it the other way round, if you sort out the connection across the LAN and then have problems via internet we will know its firewall / network issues.

Starting outside the local network we could be chasing problems on network config / security / database.

How are you planning to make the connection from the internet ?

Regards Purple|||

Quote:

Originally Posted by Purple

Hi,

Could I suggest you try it the other way round, if you sort out the connection across the LAN and then have problems via internet we will know its firewall / network issues.

Starting outside the local network we could be chasing problems on network config / security / database.

How are you planning to make the connection from the internet ?

Regards Purple

hi,
here are some details
have set it to to allow remote connections and use TCP IP only and have opened TCP port 1433 on the Windows XP firewall and am using the SQL Sever on Port UDP 3544 Also the Server Browser service is running. The server is connected directly to the internet on a static IP (eg. 10.0.0.3)

thanks and regards
riyaz|||Hi riyaz,

I suggest you follow my earlier post and get the connection working from inside the Lan first - it will make problem solving when you try from the internet so much simpler, basically we will be left with networking and access issues.

Regards Purple|||

Quote:

Originally Posted by Purple

Hi riyaz,

I suggest you follow my earlier post and get the connection working from inside the Lan first - it will make problem solving when you try from the internet so much simpler, basically we will be left with networking and access issues.

Regards Purple

Hi,

Thanks will try

riyaz