Deployment Question, Connection string issue.

When we deploy applications, we have been using DSN's set up on the
users systems. Then in the sqlconnection string, we go "dsn = xyz". I
tried this with our new application, which is the first to be done
with ADO.net and I get the following run time problem:

"An exception 'System.ArgumentException' has occured in <Myapp>".
I do the run time debugging and it tells me: "Keyword not supported:
'dsn'.

For those who have migrated to .Net, how do you handle this issue? I
mean, we are going to distribute this application, and our users will
have different names for their servers, so how do we specify a data
source dynamically.

The way we have it for the moment is that we read the information from
a config file. But it seems like there must be a better way. What
happened to dsn?

Any help on this would greatly appreciated.
Thanks,
Ed Hawkes
olaamigoquepasa@.nospamplease-hotmail.comEd Hawkes (olaamigoquepasa@.hotmail.com) writes:
> When we deploy applications, we have been using DSN's set up on the
> users systems. Then in the sqlconnection string, we go "dsn = xyz". I
> tried this with our new application, which is the first to be done
> with ADO.net and I get the following run time problem:
> "An exception 'System.ArgumentException' has occured in <Myapp>".
> I do the run time debugging and it tells me: "Keyword not supported:
> 'dsn'.
> For those who have migrated to .Net, how do you handle this issue? I
> mean, we are going to distribute this application, and our users will
> have different names for their servers, so how do we specify a data
> source dynamically.
> The way we have it for the moment is that we read the information from
> a config file. But it seems like there must be a better way. What
> happened to dsn?

If you despearately need DSN, I would suppose you could use OleDb
client rather than SqlClient.

As for what happened, I guess DSN got of fashion, and I can't say that
I miss it. Our application - which is VB6 - once used DSN, but now you
can specify server and database on the login form (and the values are
saved in registry between invocations), which I very much like. Of course,
end users normally use the same server and database, and it's only
developers like me, who change all the time. But nevertheless, DSNs
is just one more thing that has to be configured, and which could buy
settings you did not expect.

IF you don't want to prompt your users, a config file seems like a
good way to go.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <esquel@.sommarskog.se> wrote in message news:<Xns952AF310B27FBYazorman@.127.0.0.1>...
> Ed Hawkes (olaamigoquepasa@.hotmail.com) writes:
> > When we deploy applications, we have been using DSN's set up on the
> > users systems. Then in the sqlconnection string, we go "dsn = xyz". I
> > tried this with our new application, which is the first to be done
> > with ADO.net and I get the following run time problem:
> > "An exception 'System.ArgumentException' has occured in <Myapp>".
> > I do the run time debugging and it tells me: "Keyword not supported:
> > 'dsn'.
> > For those who have migrated to .Net, how do you handle this issue? I
> > mean, we are going to distribute this application, and our users will
> > have different names for their servers, so how do we specify a data
> > source dynamically.
> > The way we have it for the moment is that we read the information from
> > a config file. But it seems like there must be a better way. What
> > happened to dsn?
> If you despearately need DSN, I would suppose you could use OleDb
> client rather than SqlClient.
> As for what happened, I guess DSN got of fashion, and I can't say that
> I miss it. Our application - which is VB6 - once used DSN, but now you
> can specify server and database on the login form (and the values are
> saved in registry between invocations), which I very much like. Of course,
> end users normally use the same server and database, and it's only
> developers like me, who change all the time. But nevertheless, DSNs
> is just one more thing that has to be configured, and which could buy
> settings you did not expect.
> IF you don't want to prompt your users, a config file seems like a
> good way to go.

Erland,
much obliged! I really appreciate the response, and this will help
move our project along. Thanks again.
Cheers,
Ed Hawkessql

Deployment Problem

I get the following error while deploying on my local machine with my machin
e name or ip
A connection could not be established to the ReportServer http://machinename/Repor
tServer
If i deploy with localhost instead of machinename it works.
Any ideas why that happens.
Help would be appreciated.
ThanksI suggest you check your IIS configuration. Check the properties - web site
tab - advanced button of the Default website in IIS and see if you have
anything other than just "Default 80" under "Multiple identities for this
web site"
Tunji
"ReportFaqGuy" <anonymous@.discussions.microsoft.com> wrote in message
news:8160D89C-32CE-40C4-9A31-6066893C2048@.microsoft.com...
> I get the following error while deploying on my local machine with my
machine name or ip
> A connection could not be established to the ReportServer
http://machinename/ReportServer
> If i deploy with localhost instead of machinename it works.
> Any ideas why that happens.
> Help would be appreciated.
> Thanks
>sql

Deployment of SQLce - DATASOURCE issue

My connection string is simply

Data Source ="|DataDirectory|\Data\Test.sdf"; Password ="test";

and it runs just fine...

I did a simple publish (simple public, no checking for updates or anything)

When the public completes I run the install app. I get the following odd error during install:

************** Exception Text **************
The path is not valid. Check the directory for the database. [ Path = C:\Documents and Settings\jlibertor\Local Settings\Apps\2.0\Data\DZN9D6Y7.8E9\N0WB27KY.XZB\test..tion_b3b178185207c0b7_0001.0000_ef52a43c912d4680\Data\Data\Test.sdf ]

So... any ideas? thansk so much in advance!

have you tried;

Data Source ="|DataDirectory|\Test.sdf"; Password ="test";

Otherwise you can possibly override by using: AppDomain.Setdata

|||

OK I figured it out. ther were 2 reasons...

And if thsi helps anyone I'll past a few things:

You can set the DataDirectory using this code:

AppDomain.CurrentDomain.SetData("DataDirectory", System.AppDomain.CurrentDomain.BaseDirectory)

Place it in the application startup event.

Tip: you can't use the "My.StartupPath" in the event, and instead have to use "System.AppDomain.CurrentDomain.BaseDirectory"

ALSO

Don't forget that if you are getting this error you may not be publishing your .sdf file! (This my problem too) There are SEVERAL things you need to change in order to publich your file.

Tip: A good way to test if you are really publishign your .sdf file to check your publish package for it.

1-Set the properties of the .sdf file to "Content" and Output to "Copy Always"

2-In your Publish settings, look for yoru .sdf file. and force it to incluce.

Tip: After your user installs this once you don't want to publish it again. You'll want to change the above settings and supress this file (otherise you'll overwrite all of their hard-earned data )

Deploying to report server

I was able to deploy reports but just recently get the error "A connection
could not be made to the report server http://..../ReportServer".
Does anyone have any suggestions on what i may want to look at?
--
TabTry getting on the WebServer interface to see if the WebService is
listening, it is the same adress as you posted below,
HTH, Jens Süßmeyer.
"Tab" <Tab@.discussions.microsoft.com> schrieb im Newsbeitrag
news:B5D22565-8181-4D45-BADA-20356A9EAABD@.microsoft.com...
>I was able to deploy reports but just recently get the error "A connection
> could not be made to the report server http://..../ReportServer".
> Does anyone have any suggestions on what i may want to look at?
> --
> Tab

deploying packages

Error: 0xC0202009 at Package, Connection manager "Presup Dev sql_prov": An OLE DB error has occurred. Error code: 0x80040E4D.

An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure".

An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "TCP Provider: Se ha forzado la interrupción de una conexión existente por el host remoto.

WTF? ·%$·&$%%& i`m sure my connections are ok,, cause i prevoiusly checked them, the problem occurs when deploying the package.. it seems to be an error when connecting to the source but whyy?, and what about the package configurations ? should i use them,, and how?

Does the error message occur while you 'deploy' them or when you try to execute them after deployment. I am assuming 'deploy' at the least means they are now on another computer from where you created the package. Did you modify the package property 'protectionlevel' before you deployed? If not the default value may be causing your issues and you will want to read about the protectionlevel property in books online.

Hope that helps.

|||

in my solution proyect works fine.. so i have the deployment utility folder, then i copy it to the target computer, the error appears when i'm using the wizard to deploy it.. i`ve changed the protection level and it remains the same error... which is the correct option?

sorry if my english sucks..

|||

apparently i′ve found a possible solution.. in the project properties on the security tab.. i stablished a package password, then skept the prevalidation of the package during the deployment, once in my target server i run the package giving the password package and bingo!!! it worked.. i don`t know if this is the most viable solution but it worked anyway.. please can anybody tell me if this is the best option?

Deploying error

IIS and other things were re-installed on a machine I used to deploy to.
Now when I deploy, I get this error.
The underlying connection was closed: Unable to connect to the remote
server.
What should I check for this?Sorry, i found it in another message, changing the config file.
"Cindy Lee" <cindylee@.hotmail.com> wrote in message
news:ePRTeT$VFHA.2700@.TK2MSFTNGP12.phx.gbl...
> IIS and other things were re-installed on a machine I used to deploy to.
> Now when I deploy, I get this error.
> The underlying connection was closed: Unable to connect to the remote
> server.
> What should I check for this?
>

Deploying a report services application to the local host; error:A connection could not be made

I installed SQL reporting services 2005 and successfully configured reporting services.After designing the report using Bussiness Intelligence Studio, i tried to deploy my reporting services application to the localhost , I got the below mentioned error :

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The request failed with HTTP status 404: Not Found. (Microsoft.ReportingServices.Designer)

Can anybody provide a solution for this issue....

Thanks in advance

Nirupa

Hi Nirupa,

Can you check your Reporting Services Configuration Manager and see what the status of Report Server is?

Start>>All Programs>>MS SQL Server 2005>>Configuration Tools>>Reporting Services Configuration.

|||

Hello Viral,

Report server status in configuration manger is configured i.e report sever is connected

Thanks

Nirupa

|||

Hello Viral,

Though sql reporting manager configuration is configured correctly and reporting server status

shows "running".Except "E-mail settings" all other are showing green in color in configuration lancher page.

Still I am not able to deploy an reporting services application. It is giving same error as I previously

mentioned.

can you suggest what shall be done.

Thanks,

Nirupa

|||Have you tried opening the page http://localhost/reportserver in your browser?

Deploying a report services application to the local host; error:A connection could not be made

I installed SQL reporting services 2005 and successfully configured reporting services.After designing the report using Bussiness Intelligence Studio, i tried to deploy my reporting services application to the localhost , I got the below mentioned error :

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The request failed with HTTP status 404: Not Found. (Microsoft.ReportingServices.Designer)

Can anybody provide a solution for this issue....

Thanks in advance

Nirupa

Hi Nirupa,

Can you check your Reporting Services Configuration Manager and see what the status of Report Server is?

Start>>All Programs>>MS SQL Server 2005>>Configuration Tools>>Reporting Services Configuration.

|||

Hello Viral,

Report server status in configuration manger is configured i.e report sever is connected

Thanks

Nirupa

|||

Hello Viral,

Though sql reporting manager configuration is configured correctly and reporting server status

shows "running".Except "E-mail settings" all other are showing green in color in configuration lancher page.

Still I am not able to deploy an reporting services application. It is giving same error as I previously

mentioned.

can you suggest what shall be done.

Thanks,

Nirupa

|||Have you tried opening the page http://localhost/reportserver in your browser?

Deployed Application isn't connecting to SQL Server

When deploying my application that uses sql server it doesn't connect to the server.

I checked the connection string & it's ok the server instance is the same.

The computer name isn't the same & i use the .\SQLExpress as the data source.

I get an error saying 'sqlserver does not allow remote connections error 26 locating server / instance specified'.

Since computer name is changed, can you try to recreate the data source again? When creating a datasource, you can verify that if the datasource is ok to connect to the server.|||Another thing to look at is that if computer name is changed, the servername might not be valid. Can you run select @.@.servername to verify?|||

This link can help you.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

|||

The connection string from the dataset that visual studio generated was wrong

it needed to be .\SQLExpress thanks to all for the help

Deploy SSIS package to production which has a connection to oracle databse

Hi There,

In SSIS package development environment, I was able to connect to an oracle database and pull data into my sql server database. I installed the client tools for oracle and I put an entry into the tnsnames.ora and I was able to connect.

But in production environment, if I deploy the package on sql server, I was wondering if I had to do the same job of downloading the oracle client tools onto my production machine --which creates a tnsnames.ora file to it default location and then edit it with tthe tns entry-- or is there a better way to do this--avoiding the download?

Can somebody plzz help me ?

Thanks.

You need to install the Oracle Client (9i) or (10) on the actual SQL Server box.

This is for the network libraries. There is a special build of the client for Windows 2003 Server if you go to Oracles site and have a look around

cheers Dave

|||

You do need to repeat the same steps like you've done in your development environment: install Oracle client and adjust tnsnames.ora file.

There are 2 more options:

1) There is another "lighter" option - Oracle Instant Client:

http://www.oracle.com/technology/tech/oci/instantclient//index.html

2) The Oracle Data Provider for .NET (ODP.NET) . It has Oracle client bundled with it.

http://www.oracle.com/technology/tech/windows/odpnet/index.html

Regards,
Yitzhak

|||

Hi Yitzhak,

If I intstall the lighter option, where do I adjust the tnsnames.ora file? I don't find the file after installation. Do I need to manually create it and put it in a specific location? Can you please reply back?

Thanks.

Sam.

|||

Also, which of the instant client packages should I download? There are 5 downloads for install client for 64bit.

Thanks.

Sam.

|||

Oracle has Instant Client FAQ page:

http://www.oracle.com/technology/tech/oci/instantclient/ic-faq.html#A5028

How do I ensure that my "tnsnames.ora" file is being used in Instant Client?
Always set the TNS_ADMIN environment variable or registry setting to the full path of the tnsnames.ora file. This practice will ensure that you are using the appropriate tnsnames.ora for your application when running with Instant Client.

Regards,
Yitzhak

|||

Because you are using MS SQL Server 2005 SSIS on Windows OS, just 2 options are applicable for you:

Windows Itanium 64-bit 10.2.0.2|||

HiYitzhak,

Can you please bare with me? I downloaded the windows x86 64 bit install client and this is what I did.

I unzipped the folder contents to c:install\instantclient

I created a tnsnames.ora file with the tns entry under 'C:\'.

I added the full path 'c:install\instantclient\' to the path environment variable

I also added a tns_admin environment variable giving it a value 'C:\tnsnames.ora'.

Now I test executing the package using dtexec and I still can't connect to the oracle database. It still gives me an error 'Client and networking components not installed. Am I missing smth?

Can you please help me?

Thanks.

|||

There is a command line tnsping.exe Oracle utility to check both client installation and tnsnames.ora settings.

You can try to launch it at the command prompt:

c:\>tnsping oracle-instance-name

Regards,
Yitzhak

Deploy Shared Datasource error

Hello,
When I tried to deploy shared data sources, there is an error â'A connection
could not be made to report server to â?¦â' I donâ'tâ' what is wrongâ?¦. Could
anyone please help me to solve this problem?
Thanks in advance
ChiekoCheck the properties of the shared data source from the web folder where it
resides. I'm not sure if this is the norm, but I have to choose Connect
Using: Credentials stored securely in the report server and include a
username and password. For security purposes, use a username that has
read-only access to your database.
Hope that helps!
"chieko" wrote:
> Hello,
> When I tried to deploy shared data sources, there is an error â'A connection
> could not be made to report server to â?¦â' I donâ'tâ' what is wrongâ?¦. Could
> anyone please help me to solve this problem?
> Thanks in advance
> Chieko
>

Deploy Report error?

I try to deploy report "rptInfo.rdl" and I receive this error;
A connection could not be made to the report server
http://localhost/ReportServer.
Unable to connect to the remote server (Microsoft.ReportingServices.Designer).
What should i do to make this work?
Thanks.I reinstall my IIS and when i deploy again this report, I have a new error
message;
Error 1 The report server cannot open a connection to the report server
database. A connection to the database is required for all requests and
processing. 0 0
"GGill" wrote:
> I try to deploy report "rptInfo.rdl" and I receive this error;
> A connection could not be made to the report server
> http://localhost/ReportServer.
> Unable to connect to the remote server (Microsoft.ReportingServices.Designer).
> What should i do to make this work?
> Thanks.|||One more error i have when i try to deploy the report
-- Build started: Project: Report Project1, Configuration: Debug --
Build complete -- 0 errors, 0 warnings
-- Deploy started: Project: Report Project1, Configuration: Debug --
Deploying to http://localhost/ReportServer
Error rsReportServerDatabaseUnavailable : The report server cannot open a
connection to the report server database. A connection to the database is
required for all requests and processing.
Deploy complete -- 1 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==================== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
"GGill" wrote:
> I try to deploy report "rptInfo.rdl" and I receive this error;
> A connection could not be made to the report server
> http://localhost/ReportServer.
> Unable to connect to the remote server (Microsoft.ReportingServices.Designer).
> What should i do to make this work?
> Thanks.|||Looks like the Report Server web service cannot connect to the database. Is
this SQL Server 2005? Is so, run the configuration utility to set up a
backend database for RS. If it's SQL 2000, you may have to run Rsactivate to
provide correct database connection details.
Roman
--
Roman Rehak
http://sqlblog.com/blogs/roman_rehak
"GGill" <GGill@.discussions.microsoft.com> wrote in message
news:6FBD875E-79E9-480C-9CE5-21D45B95AA0E@.microsoft.com...
> One more error i have when i try to deploy the report
> -- Build started: Project: Report Project1, Configuration:
> Debug --
> Build complete -- 0 errors, 0 warnings
> -- Deploy started: Project: Report Project1, Configuration:
> Debug --
> Deploying to http://localhost/ReportServer
> Error rsReportServerDatabaseUnavailable : The report server cannot open a
> connection to the report server database. A connection to the database is
> required for all requests and processing.
> Deploy complete -- 1 errors, 0 warnings
> ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
> ==========> ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========> "GGill" wrote:
>> I try to deploy report "rptInfo.rdl" and I receive this error;
>> A connection could not be made to the report server
>> http://localhost/ReportServer.
>> Unable to connect to the remote server
>> (Microsoft.ReportingServices.Designer).
>> What should i do to make this work?
>> Thanks.|||Back up. Make sure RS is working. Even with no reports deployed it will
still be there.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"GGill" <GGill@.discussions.microsoft.com> wrote in message
news:6FBD875E-79E9-480C-9CE5-21D45B95AA0E@.microsoft.com...
> One more error i have when i try to deploy the report
> -- Build started: Project: Report Project1, Configuration:
> Debug --
> Build complete -- 0 errors, 0 warnings
> -- Deploy started: Project: Report Project1, Configuration:
> Debug --
> Deploying to http://localhost/ReportServer
> Error rsReportServerDatabaseUnavailable : The report server cannot open a
> connection to the report server database. A connection to the database is
> required for all requests and processing.
> Deploy complete -- 1 errors, 0 warnings
> ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
> ==========> ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========> "GGill" wrote:
>> I try to deploy report "rptInfo.rdl" and I receive this error;
>> A connection could not be made to the report server
>> http://localhost/ReportServer.
>> Unable to connect to the remote server
>> (Microsoft.ReportingServices.Designer).
>> What should i do to make this work?
>> Thanks.|||From SQL Server 2005 i am connecting to sql server 2000 database.
I try to connect to 'Reporting Services Configuration Manager' and i
received error message 'Provider load failure'.
How should i make RS work?
"Bruce L-C [MVP]" wrote:
> Back up. Make sure RS is working. Even with no reports deployed it will
> still be there.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "GGill" <GGill@.discussions.microsoft.com> wrote in message
> news:6FBD875E-79E9-480C-9CE5-21D45B95AA0E@.microsoft.com...
> > One more error i have when i try to deploy the report
> >
> > -- Build started: Project: Report Project1, Configuration:
> > Debug --
> > Build complete -- 0 errors, 0 warnings
> > -- Deploy started: Project: Report Project1, Configuration:
> > Debug --
> > Deploying to http://localhost/ReportServer
> > Error rsReportServerDatabaseUnavailable : The report server cannot open a
> > connection to the report server database. A connection to the database is
> > required for all requests and processing.
> > Deploy complete -- 1 errors, 0 warnings
> > ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
> > ==========> > ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========> >
> > "GGill" wrote:
> >
> >> I try to deploy report "rptInfo.rdl" and I receive this error;
> >>
> >> A connection could not be made to the report server
> >> http://localhost/ReportServer.
> >> Unable to connect to the remote server
> >> (Microsoft.ReportingServices.Designer).
> >>
> >> What should i do to make this work?
> >>
> >> Thanks.
>
>

Deploy Problem

I created a package, created an XML Config file, created a deployment utility and then deployed to server.

Changed Connection Managers Data Source and Initial catalog properites during deplyment. Config file in the deployment folder have the right data source and initial catalog properties value.

But when i run the package..I see wrong connection string(still showing dev server name) even though I changed during these properties during deployement and shows it right in configuration file in deployment folder.

From where the package is reading connection properties....very confusing

I will appreciate any help!!!

Amar

Don't use the data source and initial catalog properties. Use the ConnectionString property instead. At least, that's worked good for me.|||

Thanks Phil for you reply.

I have used Data Source and Initial Catalog properites in another pacakge and it worked fine...but not this time;)

|||

I even tried ConnectionString property..but still not working. I am missing something here

|||Are you sure that when you deploy the SSIS package can find the *correct* config file? It's not grabbing values from a duplicate config file sitting somewhere, is it?|||

SSIS package should use config file in deployment folder...i dont think SSIS is doing that. I cannot find any other config file.

Anything else i should check.

|||

When you right-click on the background of the control flow, do you have the XML Configuration file listed under "Package Configurations"? If yes, what directory does it point to?

Are you receiving any errors when you open up the package on the second server?

|||

Yes XML configuration file is listed under Package configurations. I am not specifying any directory path..just providing name of the config file..so that the config file is placed in deployment folder.

No..I am not getting any error on the second server.Just the connection string is wrong.

|||

Amar Khaira wrote:

Yes XML configuration file is listed under Package configurations. I am not specifying any directory path..just providing name of the config file..so that the config file is placed in deployment folder.

No..I am not getting any error on the second server.Just the connection string is wrong.

Here's the deal. I believe you *need* to specify a path. Here's why. When I opened up and saved a new XML configuration file without a full path, my config file got stored in: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE.

Then I deployed the package, and opened the package from the deployment folder (C:\Documents and Settings\Phil Brammer\My Documents\Visual Studio 2005\Projects\Test01\Test01\bin\Deployment), and the values were picked up from the IDE folder, not the deployment folder.

Check into that and use absolute paths, where possible.|||I can confirm Phil's answer, we ran into a similar problem recently. To use XML config files without the full path, you have to make sure the current working directory is the same as the directory to package is located in. If you are running DTEXEC directly, you could use a batch file to change the directory (CD) before calling DTEXEC. If you are running it from SQL Agent, the only work-around we found was to have Agent call a batch file to run DTEXEC instead of running it directly.|||

I specified path while creating XML config file...but it still does not work after deployment.I am deploying the package in File System.

But here is what i noticed. When I open package from deployment folder by clicking C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Some_FolderName\Package_Name.dtsx it shows right connection properties.

But I try to run the package from IS by right clicking the package->Connection Manager it shows wrong server name.

I am doing something terribly wrong. Please HELP!!

Amar

|||Unless you have the full SSIS client installed, when you right-click and execute a package, it is using your local machine's properties, not the remote machine's.|||I have full SSIS Client Installed.

Deploy error

Worked yesterday now I can't deploy.

Details:

===================================

A connection could not be made to the report server http://bireports/Reports. (Microsoft Semantic Model Designer)

===================================

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.SemanticQueryDesign)

Program Location:

at Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String Item)
at Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.GetItemType(String item)
at Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.CheckAuthorized()
at Microsoft.ReportingServices.ModelDesigner.Project.ModelClientManager.GetCredentials(String url)
at Microsoft.ReportingServices.ModelDesigner.Project.ModelProjectDeployer.PrepareDeploy()

===================================

The request failed with HTTP status 404: Not Found. (Microsoft.ReportingServices.SemanticQueryDesign)

Program Location:

at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String Item)

TIA

You should use the report server URL to deploy. It looks like you're using the report manager Url (http://bireports/Reports).

If you chose the default deployment options this should be http://bireports/reportserver.

Hope that helps,

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

That works.

Thanks for the help.

I did have a instance login problem after but resolved it using rsconfig.