Problems deploying to a remote Report Server(2005)

I developed a simple report using the AdventureWorks sample database on a XP
Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
preview mode. When I attempt to deploy it to a remote Report Server (June
2005 CTP) I get the following error:
"A connection could not be made to the report server
http://<servername>/reportserver.
Additional information: The version of the report server web service
definition (WSDL) is either not valid or unrecognized. The server is not a
compatible version (Microsoft.reportingServices.Designer)"
Any help/responses is greatly appreciated.
PS: The same report developed and deployed on the Report Server works fine!!
--
Thank you,
AshokThe version of RS with Beta2 is not the same as the June CTP. My guess is
that this version mismatch is causing the problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>I developed a simple report using the AdventureWorks sample database on a
>XP
> Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> preview mode. When I attempt to deploy it to a remote Report Server (June
> 2005 CTP) I get the following error:
> "A connection could not be made to the report server
> http://<servername>/reportserver.
> Additional information: The version of the report server web service
> definition (WSDL) is either not valid or unrecognized. The server is not
> a
> compatible version (Microsoft.reportingServices.Designer)"
> Any help/responses is greatly appreciated.
> PS: The same report developed and deployed on the Report Server works
> fine!!
> --
> Thank you,
> Ashok|||THanks Bruce. I appreciate your prompt reponse.
I suspected that it would be an incompatibility issue. Would you recommend
that I uninstall the Beta and install the june CTP on the client?
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> The version of RS with Beta2 is not the same as the June CTP. My guess is
> that this version mismatch is causing the problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >I developed a simple report using the AdventureWorks sample database on a
> >XP
> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> > preview mode. When I attempt to deploy it to a remote Report Server (June
> > 2005 CTP) I get the following error:
> >
> > "A connection could not be made to the report server
> > http://<servername>/reportserver.
> >
> > Additional information: The version of the report server web service
> > definition (WSDL) is either not valid or unrecognized. The server is not
> > a
> > compatible version (Microsoft.reportingServices.Designer)"
> >
> > Any help/responses is greatly appreciated.
> >
> > PS: The same report developed and deployed on the Report Server works
> > fine!!
> > --
> > Thank you,
> > Ashok
>
>|||Yes. If you have the report available from RS 2000 then I suggest
uninstalling the beta and install the CTP and then bring over the reports
from RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> THanks Bruce. I appreciate your prompt reponse.
> I suspected that it would be an incompatibility issue. Would you
> recommend
> that I uninstall the Beta and install the june CTP on the client?
> --
> Thank you,
> Ashok G
>
> "Bruce L-C [MVP]" wrote:
>> The version of RS with Beta2 is not the same as the June CTP. My guess is
>> that this version mismatch is causing the problem.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
>> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>> >I developed a simple report using the AdventureWorks sample database on
>> >a
>> >XP
>> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
>> > in
>> > preview mode. When I attempt to deploy it to a remote Report Server
>> > (June
>> > 2005 CTP) I get the following error:
>> >
>> > "A connection could not be made to the report server
>> > http://<servername>/reportserver.
>> >
>> > Additional information: The version of the report server web service
>> > definition (WSDL) is either not valid or unrecognized. The server is
>> > not
>> > a
>> > compatible version (Microsoft.reportingServices.Designer)"
>> >
>> > Any help/responses is greatly appreciated.
>> >
>> > PS: The same report developed and deployed on the Report Server works
>> > fine!!
>> > --
>> > Thank you,
>> > Ashok
>>|||I moved to another RS 2005 server that has CTP June and it worked! I was
able to publish and execute the report.
Thanks once again.
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> Yes. If you have the report available from RS 2000 then I suggest
> uninstalling the beta and install the CTP and then bring over the reports
> from RS 2000.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> > THanks Bruce. I appreciate your prompt reponse.
> > I suspected that it would be an incompatibility issue. Would you
> > recommend
> > that I uninstall the Beta and install the june CTP on the client?
> >
> > --
> > Thank you,
> > Ashok G
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> The version of RS with Beta2 is not the same as the June CTP. My guess is
> >> that this version mismatch is causing the problem.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> >> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >> >I developed a simple report using the AdventureWorks sample database on
> >> >a
> >> >XP
> >> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
> >> > in
> >> > preview mode. When I attempt to deploy it to a remote Report Server
> >> > (June
> >> > 2005 CTP) I get the following error:
> >> >
> >> > "A connection could not be made to the report server
> >> > http://<servername>/reportserver.
> >> >
> >> > Additional information: The version of the report server web service
> >> > definition (WSDL) is either not valid or unrecognized. The server is
> >> > not
> >> > a
> >> > compatible version (Microsoft.reportingServices.Designer)"
> >> >
> >> > Any help/responses is greatly appreciated.
> >> >
> >> > PS: The same report developed and deployed on the Report Server works
> >> > fine!!
> >> > --
> >> > Thank you,
> >> > Ashok
> >>
> >>
> >>
>
>

Problems continued - Cannot establish remote connection to Analysis Services

hello,

i am trying to connect to Analysis services server through another pc but i am unable to do so.

Using the following commands i manage to connect to analysis services server at my pc

Server.srv=new Server ();

srv.Connect('ip address or name');

but not to another pc. Are there any settings under sql server should i change ?

I assume that you are using Analysis Services 2005.

First, make sure that the Analysis Services allows remote connections:

On the machine running analysis services, please perform the following steps:

- All programs\Microsoft SQL Server 2005\Configuration Tools\Sql Server Surface Area Configuration

- Click on the Surface Area Configuration for Services and Connections

- Select Remote Connections under the MSSQLSERVER\Analysis Services node

- Make sure that Local and Remote connections is selected (to allow remote connections)

At this point, the client machine should be able to connect to the remote server. Before everything works, you will need to make sure that the client machine connection code is running under credentials that can access Analysis Services

|||

Well i have already enable remote connections and chech credentials as well

This is the error i am getting :

{"A connection cannot be made. Ensure that the server is running."} System.Exception {Microsoft.AnalysisServices.ConnectionException}

{"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"} System.Exception {System.Net.Sockets.SocketException}

Any help ? thanks.

|||That is unusual. Does PING work for the remote computer? Also, could you please check any firewall settings on the remote computer? Analysis Services (msmdsrv.exe) needs permissions through the firewall|||

PING works fine among the two ps's and analysis services is excepted under firewall .

I am still facing the same problem.

Can you please provide me the exact connection string from a pc1 with ip 10.181.11.1 to a pc2 with ip 10.181.11.2 (asp form in pc1 to analysis server in pc2)?

Maybe i use a wrong connection string

This is the error i am getting :

Unable to read data from the transport connection : an existing connection was forcibly closed by the remote host

Any help?

Thanks

|||

Are you using OLE DB or Adomd.Net?

The Connection String should look like "Data Source=10.181.11.2; Initial Catalog=<Your Database>"

One possible reason for the error is that your current user does not have permissions on the server. Are the computers in the same domain? If not, is Everyone allowed to access a database on the server?

|||

I am using ADOMD connection,,if you have an example connection string it would be helpful to check with the one i use

(i have tried different ways of setting the connection string but still cannot connect ).

As far as user credentials are concerned i have also tried to set them in different ways.

I am not quite sure which user (WinXP user, Database Engine User , IIS user, Analysis Services user) must have access to which place,, i am a bit confused about this.

I appreciate your help. Thank you

|||

To begin, let's make sure the physical connection works correctly. On the Analysis Services machine, create a new Analysis Services role which has permissions on your target database, and make sure that Everyone is a member of that role.

Then, try to connect from your client machine, using a connection string like

"Data Source=<IP of the remote machine>; Initial catalog=<name of the DB which is accessible to Everyone>"

If this works, the physical connection is OK and we'll focus on credentials.

Are your machines part of the same Windows NT domain? Tell me a few things about your application, I understand it is a web application, is it correct? Is it impersonating the remote user or running uner a set of specified credentials, or running under the default credentials (machine\ASPNET user)?

And, if you don't mind, could you please reply to this thread rather than creating a new post? It is easier to keep track of the issues

|||

We did what you suggested but we still get the same error.

Do we need to give the permissions and to the actual database (database engine) except to the one in analysis services ?

Our machines are part of the same workgroup connected via a router.

It is a web application and it is runnig under the default credentials.

But we tried with a windows application to check if we can connect to the analysis services and we still get the error

We can access a remote database engine througn sql server management studio but not remote analysis services server.

Is there a way to access a remote analysis services through sql server management studio?

Thanks

|||

This reply involves another error (not the one mentioned above). It seems to have a problem in creating the DIMENSION through source code and the problem seems to be on 'Process' command. We removed the Process command from the code and tried to process it through anaysis services management studio and still got error 'process failed' . This is a critical issue ,,i cannot continue to create cubes, etc.

As far as my application is concerned ,,it is a web application ,,the user will choose through an asp form measures and dimensions and then dimensions,cubes,structures will be created dynamically. So the problem is at initial state since i cannot create the dimenions.

Pls help.

This is the source code i use for dimension creation :

static void CreateDateDimension(Database db)

{

// Create the Date dimension

Dimension dim = db.Dimensions.Add("Invitquest");

dim.Type = DimensionType.Time;

dim.UnknownMember = UnknownMemberBehavior.Hidden;

dim.AttributeAllMemberName = "All Periods";

dim.Source = new DataSourceViewBinding(datasourceName);

dim.StorageMode = DimensionStorageMode.Molap;

#region Create attributes

DimensionAttribute attr;

attr = dim.Attributes.Add("Invitquest");

attr.Usage = AttributeUsage.Key;

attr.Type = AttributeType.Date;

attr.OrderBy = OrderBy.Key;

attr.KeyColumns.Add(CreateDataItem(db.DataSourceViews[0], "Invitquest", "invno"));

// attr.NameColumn = CreateDataItem(db.DataSourceViews[0], "Invitquest", "tableid");

attr = dim.Attributes.Add("YPopto");

attr.Type = AttributeType.Regular;

attr.KeyColumns.Add(CreateDataItem(db.DataSourceViews[0], "Invitquest", "Ypopto"));

// attr.NameColumn = CreateDataItem(db.DataSourceViews[0], "Invitquest", "Ypopto");

attr = dim.Attributes.Add("cancer");

attr.Type = AttributeType.Regular;

attr.KeyColumns.Add(CreateDataItem(db.DataSourceViews[0], "Invitquest", "CANCER"));

// attr.NameColumn = CreateDataItem(db.DataSourceViews[0], "Invitquest", "CANCER");

attr = dim.Attributes.Add("AM BIO");

attr.Type = AttributeType.Regular;

attr.KeyColumns.Add(CreateDataItem(db.DataSourceViews[0], "Invitquest", "AMBIO"));

// attr.NameColumn = CreateDataItem(db.DataSourceViews[0], "Invitquest", "AMBIO");

#endregion

dim.Update();

}

Thanks.

|||I merged all these threads.|||

> Our machines are part of the same workgroup connected via a router.

This seems to be the issue. Analysis Services uses exclusively Windows Integrated security. User accounts are not shared across machines in a workgroup, only in a domain (or related domains). This might explain both the management studio failure as well as the custom application failure.

Can you try allowing Everyone access to the Analysis Services database? Eventually , the permissions for the Everyone role can be restricted to what is needed (most likely, Read Definition and predictions), but you can start with Everyone as administrator -- not a great security suggestion, but it allows you to easily figure out if this is the source of the problem.

sql

Problems connectiong to a remote DB

Hello

I developed a vb.net win app which interacts with a sqlserver 2005 express DB.

When the DB is located in my local computer everything works just fine.

I'm trying to connect to a remote DB (mdf file that located on a remote server) but without any success.

I assume that a connectionstring change is needed, however I can't find what change to perform (I tried to insert the server IP address to the connectionstring but it didn't work either).

the app connectionstring looks like that:

connectionString

="Data Source=.\SQLExpress;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\DBName.mdf;Integrated Security=True;User Instance=False" providerName="System.Data.SqlClient" />

Hope someone can help me find the solution.

Since your question concerns a Windows Forms application, and not ASP.NET, you should ask it on theMSDN Forums.|||Try looking atwww.connectionstrings.com...|||Hi yarit, post the connection failure error message would help to solve the issue. You can also take a look at this post:
http://forums.asp.net/thread/1289341.aspx|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||Hi yairt, first of all you have to make sure on teh SQL box no firewall is blocking TCP/IP communication to the SQL Express service from Internet. You can use telnet to check this, please refer to the post I mentioned in my previous post.|||

hi Iori jay

thanks for your reply.

The problem was solved (or better said was by-passed), apparently it has nothing to do with SQLSERVER or connection strings.

We connected the server to the internet via ADSL line (`and not through a router that probably concealed its address) and everything worked just fine.

Problems connecting to SQL 2005 DB on server

Hi - I have Web Developer, SQL Express 2005 running locally on my pc, and on my remote server.

Everything is fine locally, but when I copy my files over to my server (have setup a virtual dir, and ensured it is running .net2) I get the following message when trying to connect:

An attempt to attach an auto-named database for file C:\websites\sickness\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

I have tried attaching and detaching the database from within SSME on the server - my connection string is:

<connectionStrings>
<add name="SicknessConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Database.mdf;Integrated Security=True;User Instance=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

I've tried it with and without the User Instance = True set

Has anyone got an actual fix for this?

Thanks, Mark

Hi - I'm sorry for bumping this, but I'm sure I can't be the only person with this problem - is there a more appropriate place I should look for an answer?

Kind regards,

Mark|||

mtait wrote:

is there a more appropriate place I should look for an answer?

Yes, I've now moved this question from the Getting Started forum to this SQL Server forum.|||I am pretty sure the problem is that you are missing the Database attribute for your connection string. I always usehttp://www.connectionstrings.com/ as a connection string reference. Drill down under SQL Server 2005 and look at the 2 SQL Server Express connection string examples. I think this will help you.|||

Hi - thank you - I was using connectionstrings.com - but each one fails.

I've now reinstalled SQL Express, and allowed Mixed Mode.

From SSME I've set the sa password to 'Bob99' and use this connection string:

<connectionStrings>

<add name="SicknessConnectionString" connectionString="Server=.\SQLExpress;Database=sickdb;User ID=sa;Password=Bob99;Trusted_Connection=False"

providerName="System.Data.SqlClient" />
</connectionStrings>

...and now the error is:

System.Data.SqlClient.SqlException: Cannot open database "sickdb" requested by the login. The login failed.
Login failed for user 'sa'.

I've checked, and rechecked the sa password - again, thanks for any help on this.

Mark

|||

Try detaching the database. You've permanently attached it, or you already have a database named 'database' on the other server. I notice that now you are calling it 'sickdb'. You could try renaming the database.mdf to sickdb.mdf as well. Then go back to your original connection string (of course you will need to change the reference from database.mdf to sickdb.mdf).

Just an FYI - your last error message is saying the userid/password is fine, but that user has no access to the 'sickdb' database. You can of course at this point go forwards and assign sa rights to the database, or you can go back and fix the original problem and not worry about permissions at all.

|||

Hi - thanks again for the help.

I think I've messed things up somewhere - I'm trying to change too many things to make this work, and I still end up with the same error messages.

If I uninstall SQL Express 2005, and do a clean install, with mixed mode authentication, is there a step by step guide anywhere which will advise how to:

a) setup a new user from within SSME
b) whether to attach the database file or not
c) which section of SSME to change to allow the user to connect to the local (database is on the same remote server as IIS) database - whether in Security/Logins or Database/Properties
d) advise a connection string which would work given the above steps#

Sorry - I know people are trying to help me, but I've just got myself completely mixed up here.

Thanks, Mark

sql

problems connecting to remote SQL Server 2005

I'm using Visual Studio 2005 Pro and am attempting to connect to a remote SQL Server 2005. I have the server name, SQL login credentials, and database name. However, when I try connecting I get this error:

"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)"

I know that remote access is enabled because I received the connection instructions directly from the database administrator. I've tried turning off my firewall. I've tried connecting with Data source: Microsoft SQL Server using both Data providers: ".NET Framework Data Provider for SQL Server" and ".NET Framework Data Provider for OLE DB". Nothing seems to work.

Any suggestions for what I may be doing wrong? Do I have to have certain software installed on my computer to make this work (other that VS2005)?

-Mathminded

You have to configure SQL Server for remote connection and it is covered in the thread below, post again if you still need help. Hope this helps.

http://forums.asp.net/thread/1379211.aspx

|||

Thanks, Caddre. Just to clarify, I am trying to connect to a remote SQL Server 2005 that is maintained by someone else. They already have remote access enabled, but I haven't been able to connect to it. They have hundreds of users and the rest of them are connecting fine. Do I also have to enable remote access on my local SQL Express installation in order to connect to their server? It seems counterintuitive to me so I want to double-check before I spend several MORE hours trying to get this to work.

Thanks!

|||

I see your point but there are many reason for such problem so it takes time, I have found two troubleshooting links provided by Microsoft and another provided by another developer, run through the check list and post again if none works. Hope this helps.

http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx

http://blogs.msdn.com/sql_protocols/archive/2006/04/21/581035.aspx

http://geekswithblogs.net/timh/archive/2006/01/30/67586.aspx

|||

Thanks again, Caddre. I really appreciate your help. I've checked out all that information but it hasn't led me to a solution. I hate to give up an entire night of work, but I'm going to have to give up on this for now and try again tomorrow. If I come up with anything, I'll post it.

Thanks! :-)

|||If those did not work then it is either connection string or permissions you need to check back with them I hope you are not having this problem with Godaddy because users always run into problem with them. Hope this helps.|||

Problem solved! :-) It turns out they had never had a remote user have to access the SQL server from outside the company, so it was a firewall issue. They added my IP as an exception and it worked flawlessly. Thanks again, Caddre, for your willingness to help. I really appreciate it.

-Mathminded

|||

Problem solved! :-) It turns out they had never had a remote user have to access the SQL server from outside the company, so it was a firewall issue. They added my IP as an exception and it worked flawlessly. Thanks again, Caddre, for your willingness to help. I really appreciate it.

-Mathminded

|||

I am glad to see your problem was resolved but fire wall addressed in the protocol troubleshooting link I gave you.

http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx

|||

You're right, it was in those lists. That was one of the things I tried checking last night and one of the reasons I decided to give up. Unfortunately, there is no way (that I know of) to know with certainty that you are being blocked by a firewall. Last night I did try to ping and telnet to the server (two things from the links you provided) but when that didn't work it either meant they had disabled those functions OR I was being blocked by a firewall.

I'm glad you replied. I had marked the thread as resolved but hadn't remembered to mark your post as the answer. I don't know how the whole points thing works on this site, but if that's how people get points I wanted to make sure you got them.

Thanks again for all your help.

-Mathminded

|||Fire wall always block database and web server, it is the second thing to check after the configuration of the server and the points are not important to me anymore I have moved on from that subject, I always post again as needed so it will help future users with same problem.sql

Problems connecting to MSDE through ADO.NET

Hi there,
i've installed MSDE and have successfully connected to it from a remote version of Enterprise Manager but when i try to connect using ADO.NET from a website using the same login details i get the following message:
"SQL Server does not exist or access denied"
I installed msde with DISABLENETWORKPROTOCOLS=0 and SECURITYMODE=SQL so everything should be setup properly.
My connection string looks like this:
server=ip_address\instance_name;uid=myusername;pwd=mypassword;database=mydatabase
This connection string works fine when testing locally (without ip address ie. localhost\instance_name)
Any ideas why this doesn't work??You need to check that if the user has accessto the database. For most hosting companies they provide ASPNET useraccount and also NETWORK users. Give permission to ASPNET user and seeif it works also try the same for NETWORK users.

|||Thanks for the reply, you've lost me a bit though. I've setup my own server using Apache and mod_aspdotnet and have successfully tested it remotely from asp.net pages connecting to a MySQL database also on my server. Now i wish to use MSDE and am getting this problem.
How do i setup an ASPNET user account and give it permission to use the database? And why do i need to?
cheers

problems connecting remotely to sql server 2005

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

|||

I merged these threads as they appear to be duplicates.

Are you using SSIS? If not, you might want to post in the SQL Server Data Access forum.

As a quick thought, you have the security set to a trusted connection, which means you don't have to specify a user id and password. You might want to take a look at http://www.connectionstrings.com/.

|||that was weird... when i tried a different connection string without the trusted connection then configured the surface area of the sql server for remote access it just connected like magic. hehe. sorry for being so bad at this btw. i already figured out how to connect to the server using the add data connection wizard in VS2K5 but i was wondering how do i access the data using this connection? how do i open it? coz in the old style we still need a manually configure a connection string, connect it and then do the queries.|||Still not clear on whether this is SSIS - in SSIS, you'd add a new connection manager (in the lower pane in the designer) to use a connection.

Problems Connect a Network Drive with SQL Server Agent

Hello
I have MS SQL 7.00.1094 on NT 4.0
When I connect a Network Drive (net use.../User:local User
on Remote System) with SQL Server Agent I cannot access
this.
If I take the same command on the desktop (Command Shell)
the access is o.K.
The SQL Server Agent is started with the same Account as I
logged on locally.
Even I connect a network drive z.B. U: local, I can not
access this from SQL Server Agent though is the same
global user.
But this Problem exist only 7 days ago.
Thanks
MartinDid someone add a proxy account to the SQL agent? Go to Enterprise Manger
and check the properties for SQL server agent | Job System tab. You should
verify then that you can map the drive with the proxy account.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Martin" <anonymous@.discussions.microsoft.com> wrote in message
news:106b801c3f46d$5ee8bef0$a301280a@.phx
.gbl...
> Hello
> I have MS SQL 7.00.1094 on NT 4.0
> When I connect a Network Drive (net use.../User:local User
> on Remote System) with SQL Server Agent I cannot access
> this.
> If I take the same command on the desktop (Command Shell)
> the access is o.K.
> The SQL Server Agent is started with the same Account as I
> logged on locally.
> Even I connect a network drive z.B. U: local, I can not
> access this from SQL Server Agent though is the same
> global user.
> But this Problem exist only 7 days ago.
> Thanks
> Martin|||A service, such as SQL Server Agent, is not supposed to be able to see
mapped drives. You should use a URL from a service.
180362 INFO: Services and Redirected Drives
http://support.microsoft.com/?id=180362
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Problem:fail to invoke remote RPC method

I have two xp sp2 machines(one desktop with sql server running, the other is
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc working
Try turning off Norton internet worm protection...
Stuart
"SP" wrote:

> I have two xp sp2 machines(one desktop with sql server running, the other is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the options
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>
|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:

Problem:fail to invoke remote RPC method

I have two xp sp2 machines(one desktop with sql server running, the other is
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp
2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc working Try turning off Norton internet worm protection...
Stuart
"SP" wrote:

> I have two xp sp2 machines(one desktop with sql server running, the other
is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the
sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the option
s
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:
>

problem with varchar and nvarchar datatype in linked server

Hi,

I am updating a remote table using linked server in sql server 2005.

but in case of varchar and nvarchar i am getting an error :

"OLE DB provider "SQLNCLI" for linked server "LinkedServer1" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

Msg 16955, Level 16, State 2, Line 1

Could not create an acceptable cursor."

thanks in advance.

Thanks & Regards

Pintu

Pintu, I had a similar problem with deleting rows through a linked sever from SQL Server 2005. I tried from SQL Server 2000 and got a slightly different error :-

"The provider could not support a row lookup position. The provider indicates that conflicts occurred with other properties or requirements."

which led me to this article:-

http://support.microsoft.com/kb/814581

which solved my problem. Hope it helps you too.

problem with varchar and nvarchar datatype in linked server

Hi,

I am updating a remote table using linked server in sql server 2005.

but in case of varchar and nvarchar i am getting an error :

"OLE DB provider "SQLNCLI" for linked server "LinkedServer1" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

Msg 16955, Level 16, State 2, Line 1

Could not create an acceptable cursor."

thanks in advance.

Thanks & Regards

Pintu

Pintu, I had a similar problem with deleting rows through a linked sever from SQL Server 2005. I tried from SQL Server 2000 and got a slightly different error :-

"The provider could not support a row lookup position. The provider indicates that conflicts occurred with other properties or requirements."

which led me to this article:-

http://support.microsoft.com/kb/814581

which solved my problem. Hope it helps you too.

Problem with update tables on linked Sybase server

While working on MsSQL 2000 I'm trying to update table on remote server
(Sybase)
Here is the description of remote table (Sybase)
IF OBJECT_ID('adm.TransClient') IS NOT NULL
drop table adm.TransClient
go
CREATE TABLE adm.TransClient
(
CUST_ID numeric(10,0) NOT NULL,
NAME varchar(254) NOT NULL,
ADR1 varchar(254) NOT NULL,
ADR2 varchar(254) NOT NULL,
CREDIT numeric(17,9) NOT NULL,
SALES varchar(30) NOT NULL,
INN varchar(30) NULL,
TYPEC smallint NOT NULL,
NO_NDS smallint NOT NULL,
NUM_DOG varchar(20) NOT NULL,
LOGIN varchar(16) NOT NULL,
BusinessGroup numeric(10,0) DEFAULT 0 NOT NULL,
TransType varchar(20) DEFAULT "insert" NOT NULL,
TransDate datetime DEFAULT getdate() NOT NULL,
Transferred smallint DEFAULT 0 NOT NULL,
CONSTRAINT PK1
PRIMARY KEY NONCLUSTERED (CUST_ID)
)
LOCK datarows
go
1. Doing like this
update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1
MsSQL returns:
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: Query-based update failed because the row
to update could not be found.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::SetData
returned 0x80004005: ].
2. Second atempt
update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1 where CUST_ID=7
MsSQL returns:
1 row affected
3. Final shoot - I wrote simpliest cursor that goes throw rows and sets
Transferred=1
Althogh MsSQL has returned:
Remote tables are not updatable. Updatable keyset-driven cursors on remote
tables require a transaction with the REPEATABLE_READ or SERIALIZABLE
isolation level spanning the cursor.
After that
select count(*) from BILLING_ASE12.billing.adm.TransClient = 300
select count(*) from BILLING_ASE12.billing.adm.TransClient where
Transferred=1 = 202 !!!!!!!
select count(*) from BILLING_ASE12.billing.adm.TransClient where
Transferred=0 = 48 !!!!!!!!
No comments from my side - simply do not understand what is going on
Any answers are appreciated
Hi
0x80004005 = Access Denied. Check that you have permissions on the
destination server for what you are doing.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Viacheslav" <Viacheslav@.discussions.microsoft.com> wrote in message
news:2F06080B-EEC4-4D91-A133-AE0C3E3923B6@.microsoft.com...
> While working on MsSQL 2000 I'm trying to update table on remote server
> (Sybase)
> Here is the description of remote table (Sybase)
> IF OBJECT_ID('adm.TransClient') IS NOT NULL
> drop table adm.TransClient
> go
> CREATE TABLE adm.TransClient
> (
> CUST_ID numeric(10,0) NOT NULL,
> NAME varchar(254) NOT NULL,
> ADR1 varchar(254) NOT NULL,
> ADR2 varchar(254) NOT NULL,
> CREDIT numeric(17,9) NOT NULL,
> SALES varchar(30) NOT NULL,
> INN varchar(30) NULL,
> TYPEC smallint NOT NULL,
> NO_NDS smallint NOT NULL,
> NUM_DOG varchar(20) NOT NULL,
> LOGIN varchar(16) NOT NULL,
> BusinessGroup numeric(10,0) DEFAULT 0 NOT NULL,
> TransType varchar(20) DEFAULT "insert" NOT NULL,
> TransDate datetime DEFAULT getdate() NOT NULL,
> Transferred smallint DEFAULT 0 NOT NULL,
> CONSTRAINT PK1
> PRIMARY KEY NONCLUSTERED (CUST_ID)
> )
> LOCK datarows
> go
> 1. Doing like this
> update BILLING_ASE12.billing.adm.TransClient
> set [Transferred]=1
> MsSQL returns:
> OLE DB provider 'MSDASQL' reported an error.
> [OLE/DB provider returned message: Query-based update failed because the
row
> to update could not be found.]
> OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::SetData
> returned 0x80004005: ].
> 2. Second atempt
> update BILLING_ASE12.billing.adm.TransClient
> set [Transferred]=1 where CUST_ID=7
> MsSQL returns:
> 1 row affected
>
> 3. Final shoot - I wrote simpliest cursor that goes throw rows and sets
> Transferred=1
> Althogh MsSQL has returned:
> --
> Remote tables are not updatable. Updatable keyset-driven cursors on remote
> tables require a transaction with the REPEATABLE_READ or SERIALIZABLE
> isolation level spanning the cursor.
> --
> After that
> select count(*) from BILLING_ASE12.billing.adm.TransClient = 300
> select count(*) from BILLING_ASE12.billing.adm.TransClient where
> Transferred=1 = 202 !!!!!!!
> select count(*) from BILLING_ASE12.billing.adm.TransClient where
> Transferred=0 = 48 !!!!!!!!
> No comments from my side - simply do not understand what is going on
> Any answers are appreciated
|||Surely I have access to this server
Otherwise I couldn't do
update no.2
(update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1 where CUST_ID=7)
that completed successfully
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> 0x80004005 = Access Denied. Check that you have permissions on the
> destination server for what you are doing.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Viacheslav" <Viacheslav@.discussions.microsoft.com> wrote in message
> news:2F06080B-EEC4-4D91-A133-AE0C3E3923B6@.microsoft.com...
> row
>
>

Problem with update tables on linked Sybase server

While working on MsSQL 2000 I'm trying to update table on remote server
(Sybase)
Here is the description of remote table (Sybase)
IF OBJECT_ID('adm.TransClient') IS NOT NULL
drop table adm.TransClient
go
CREATE TABLE adm.TransClient
(
CUST_ID numeric(10,0) NOT NULL,
NAME varchar(254) NOT NULL,
ADR1 varchar(254) NOT NULL,
ADR2 varchar(254) NOT NULL,
CREDIT numeric(17,9) NOT NULL,
SALES varchar(30) NOT NULL,
INN varchar(30) NULL,
TYPEC smallint NOT NULL,
NO_NDS smallint NOT NULL,
NUM_DOG varchar(20) NOT NULL,
LOGIN varchar(16) NOT NULL,
BusinessGroup numeric(10,0) DEFAULT 0 NOT NULL,
TransType varchar(20) DEFAULT "insert" NOT NULL,
TransDate datetime DEFAULT getdate() NOT NULL,
Transferred smallint DEFAULT 0 NOT NULL,
CONSTRAINT PK1
PRIMARY KEY NONCLUSTERED (CUST_ID)
)
LOCK datarows
go
1. Doing like this
update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1
MsSQL returns:
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: Query-based update failed because the
row
to update could not be found.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::SetData
returned 0x80004005: ].
2. Second atempt
update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1 where CUST_ID=7
MsSQL returns:
1 row affected
3. Final shoot - I wrote simpliest cursor that goes throw rows and sets
Transferred=1
Althogh MsSQL has returned:
--
Remote tables are not updatable. Updatable keyset-driven cursors on remote
tables require a transaction with the REPEATABLE_READ or SERIALIZABLE
isolation level spanning the cursor.
--
After that
select count(*) from BILLING_ASE12.billing.adm.TransClient = 300
select count(*) from BILLING_ASE12.billing.adm.TransClient where
Transferred=1 = 202 !!!!!!!
select count(*) from BILLING_ASE12.billing.adm.TransClient where
Transferred=0 = 48 !!!!!!!!
No comments from my side - simply do not understand what is going on
Any answers are appreciatedHi
0x80004005 = Access Denied. Check that you have permissions on the
destination server for what you are doing.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Viacheslav" <Viacheslav@.discussions.microsoft.com> wrote in message
news:2F06080B-EEC4-4D91-A133-AE0C3E3923B6@.microsoft.com...
> While working on MsSQL 2000 I'm trying to update table on remote server
> (Sybase)
> Here is the description of remote table (Sybase)
> IF OBJECT_ID('adm.TransClient') IS NOT NULL
> drop table adm.TransClient
> go
> CREATE TABLE adm.TransClient
> (
> CUST_ID numeric(10,0) NOT NULL,
> NAME varchar(254) NOT NULL,
> ADR1 varchar(254) NOT NULL,
> ADR2 varchar(254) NOT NULL,
> CREDIT numeric(17,9) NOT NULL,
> SALES varchar(30) NOT NULL,
> INN varchar(30) NULL,
> TYPEC smallint NOT NULL,
> NO_NDS smallint NOT NULL,
> NUM_DOG varchar(20) NOT NULL,
> LOGIN varchar(16) NOT NULL,
> BusinessGroup numeric(10,0) DEFAULT 0 NOT NULL,
> TransType varchar(20) DEFAULT "insert" NOT NULL,
> TransDate datetime DEFAULT getdate() NOT NULL,
> Transferred smallint DEFAULT 0 NOT NULL,
> CONSTRAINT PK1
> PRIMARY KEY NONCLUSTERED (CUST_ID)
> )
> LOCK datarows
> go
> 1. Doing like this
> update BILLING_ASE12.billing.adm.TransClient
> set [Transferred]=1
> MsSQL returns:
> OLE DB provider 'MSDASQL' reported an error.
> [OLE/DB provider returned message: Query-based update failed because the[/vbco
l]
row[vbcol=seagreen]
> to update could not be found.]
> OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::SetData
> returned 0x80004005: ].
> 2. Second atempt
> update BILLING_ASE12.billing.adm.TransClient
> set [Transferred]=1 where CUST_ID=7
> MsSQL returns:
> 1 row affected
>
> 3. Final shoot - I wrote simpliest cursor that goes throw rows and sets
> Transferred=1
> Althogh MsSQL has returned:
> --
> Remote tables are not updatable. Updatable keyset-driven cursors on remote
> tables require a transaction with the REPEATABLE_READ or SERIALIZABLE
> isolation level spanning the cursor.
> --
> After that
> select count(*) from BILLING_ASE12.billing.adm.TransClient = 300
> select count(*) from BILLING_ASE12.billing.adm.TransClient where
> Transferred=1 = 202 !!!!!!!
> select count(*) from BILLING_ASE12.billing.adm.TransClient where
> Transferred=0 = 48 !!!!!!!!
> No comments from my side - simply do not understand what is going on
> Any answers are appreciated|||Surely I have access to this server
Otherwise I couldn't do
update no.2
(update BILLING_ASE12.billing.adm.TransClient
set [Transferred]=1 where CUST_ID=7)
that completed successfully
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> 0x80004005 = Access Denied. Check that you have permissions on the
> destination server for what you are doing.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Viacheslav" <Viacheslav@.discussions.microsoft.com> wrote in message
> news:2F06080B-EEC4-4D91-A133-AE0C3E3923B6@.microsoft.com...
> row
>
>