I have old report built by Report Builder 18 years ago that needs to be migrated to a new Report Server Project.
I donwloaded MineDataSource.rsds (not rds) deployed by third party choco from server side.
<?xml version="1.0" encoding="UTF-8"?>
<DataSourceDefinition>
<Extension>ODBC</Extension>
<ConnectString>Dsn=mydsnsdsn=SQLEngine_Kerberos;hst=myhs;prt=19990</ConnectString>
<UseOriginalConnectString>False</UseOriginalConnectString>
<OriginalConnectStringExpressionBased>False</OriginalConnectStringExpressionBased>
<CredentialRetrieval>Integrated</CredentialRetrieval>
<Enabled>True</Enabled>
</DataSourceDefinition>
I don't want to change the shared data sources from reporting server since it may impact deployment process (from third party)+ domain account of SQLEngine_Kerberos security (set by third party).
I tried,
Add Existing data source by http://localhost//DataSources/MineDataSource.rsds, but could not find it.
merge following xml config to new .rds but not working either
<DataSources>
<DataSource Name="MineDataSource">
<DataSourceReference>/DataSources/MineDataSource</DataSourceReference>
<rd:SecurityType>None</rd:SecurityType>
<rd:DataSourceID>3f352f12-279a-4b49-9083-1e7279bdce3e</rd:DataSourceID>
</DataSource>
</DataSources>
To
<RptDataSource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="MineDataSource">
<DataSourceReference>http://localhost/<ReportServer>/MineDataSource.rsds</DataSourceReference>
<!--<DataSourceReference>/DataSources/MineDataSource</DataSourceReference>-->
<SecurityType>None</SecurityType>
<DataSourceID>d72617f8-1c7f-43d3-b9de-7dfc57d7afd6</DataSourceID>
</RptDataSource>
Anything that I could try? or you have right rds file to handle DataSourceReference?
Thanks a lot
Related
I've set up a local directory (C:\NuGet) to contain local NuGet packages. I then hosted this location on IIS (localhost:619). I then added this location in my NuGet.Config file like this:
<packageSources>
<remove key="Local" />
<add key="Local" value="http://localhost:619/" />
</packageSources>
When i open the package manager i get the following error:
[Local] The V2 feed at 'http://localhost:619/Search()?$filter=IsAbsoluteLatestVersion&searchTerm=''&targetFramework='net452'&includePrerelease=true&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '404 Not Found'.
Is there a way to get around this error or make this work?
NuGet only supports .nupkgs in a folder for filesystem based feeds (URLs that can be represented using file://). Any HTTP feed must implement one of the NuGet HTTP protocols. The link billybob posted as a comment to your question lists several NuGet servers that you can host on your web server.
I'll point out Sleet, written by a former member of Microsoft's NuGet team. It's a static site generator, meaning it creates a bunch of files, and then you just serve those files the same way you're currently trying to serve the .nupkgs, it doesn't need a web app that dynamically generates content, or a database. But every time you add remove a .nupkg, you need to regenerate all the static files.
Alternatively, you could just use a network file share, rather than HTTP. Although it's inefficient if your developers use Visual Studio's Package Manager UI to search for packages, so you'd really be better off with any HTTP feed if you have a lot of .nupkgs.
I am a newbie to BizTalk development, having only been using it properly for 6-7 weeks, so forgive my naivety.
I have a basic BizTalk 2013 application in development and am ready to deploy to a test environment.
I am using business rules to define the Outbound Transport Location, after all transform have been done, this sends the data to a stored procedure in SQL Server, which inserts/updates the record:
mssql://.//db1?
When we deploy to our test/live environments, we will not be able to set the Outbound Transport Location to the local machine as the databases will be stored on separate servers to the application. For example:
mssql://dbserver//db1?
I have looked through the BizTalk Deployment Framework to see if business rules can be modified depending on environment, but couldn't find anything.
So my question is, what is the best (lowest maintenance) way to manage environment based settings for business rules? Using the BizTalk Deployment Framework would be preferable.
I'll post the solution I used for future reference and to help anyone who comes across this in the future.
In the BizTalk Deployment Framework, it is possible to add additional XML files to the build, and pre-process them in the same way binding files are pre-processed depending on environment.
Below are some snippets from the deployment.btdfproj file. Don't forget that with the BizTalk Deployment Framework, order is essential:
<!-- Add the policy file as an additional item to the build -->
<ItemGroup>
<AdditionalFiles Include="my_policy_file.xml">
<LocationPath>..\$(ProjectName)\location_to_policy</LocationPath>
</AdditionalFiles>
</ItemGroup>
<!-- Processes the additional XML policy files added to the MSI main build folder. -->
<ItemGroup>
<FilesToXmlPreprocess Include="my_policy_file.xml">
<LocationPath>..\</LocationPath>
</FilesToXmlPreprocess>
</ItemGroup>
<!-- You still have to add the business rule to the build. It is overwritten later. -->
<ItemGroup>
<RulePolicies Include="my_policy_file.xml">
<LocationPath>..\$(ProjectName)\location_to_property</LocationPath>
</RulePolicies>
</ItemGroup>
<!-- Towards the end of the file the pre-processed file overwrites the originally included policy file. -->
<Target Name="CopyXMLPreprocessedPoliciesToBRE" AfterTargets="PreprocessFiles">
<copy sourceFiles="..\my_policy_file.xml" DestinationFolder="..\BRE\Policies"/>
</Target>
For more information, check out this thread on the BizTalk Deployment Framework site: https://biztalkdeployment.codeplex.com/discussions/392801
I just installed VS 2013, upgrading from VS 2010. Creating a web deployment package zip file used to work in 2010. using VS 2013's Publish Web feature to publish to a Web Deploy Package, I getting the following error:
Web deployment task failed. (Object of type 'manifest' and path
'D:\dev\DMWeb\DMWebClient\obj\Test\Package\DMWebClient.SourceManifest.xml'
cannot be created. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT.)
The details in the Web Publish Activity tab shows the following:
Transformed Web.config using D:\dev\DMWeb\DMWebClient\Web.Test.config
into obj\Test\TransformWebConfig\transformed\Web.config.
Auto ConnectionString Transformed Views\Web.config into
obj\Test\CSAutoParameterize\transformed\Views\Web.config.
Auto ConnectionString Transformed obj\Test\TransformWebConfig\transformed\Web.config into
obj\Test\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish: obj\Test\Package\PackageTmp.
Packaging into D:\dev\DMWeb\DMWebClient\obj\Test\Package\DMWebClient.zip.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(3883,5):
Error ERROR_EXCEPTION_WHILE_CREATING_OBJECT: Web deployment task failed. (Object of type 'manifest' and path
'D:\dev\DMWeb\DMWebClient\obj\Test\Package\DMWebClient.SourceManifest.xml' cannot be created.
Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT.)
Package failed.
In VS 2010, I've had to run it as Administrator for deploy to work, and I'm doing so here as well. I've also tried giving Full Control permissions to the project folder to NETWORK SERVICE, LOCAL SERVICE, Authenticated Users, and myself.
In the Package folder, there is the PackageTmp folder (which looks good), and the DMWebClient.SourceManifest.xml file, and that's it. In VS 2010, there's more files there.
DMWebClient.SourceManifest.xml contains:
<?xml version="1.0" encoding="utf-8"?>
<sitemanifest>
<IisApp path="D:\dev\DMWeb\DMWebClient\obj\Test\Package\PackageTmp" />
<setAcl path="D:\dev\DMWeb\DMWebClient\obj\Test\Package\PackageTmp" setAclResourceType="Directory" />
<setAcl path="D:\dev\DMWeb\DMWebClient\obj\Test\Package\PackageTmp" setAclUser="anonymousAuthenticationUser" setAclResourceType="Directory" />
<setAcl path="D:\dev\DMWeb\DMWebClient\obj\Test\Package\PackageTmp\App_Data" setAclResourceType="Directory" setAclAccess="Write" />
<setAcl path="D:\dev\DMWeb\DMWebClient\obj\Test\Package\PackageTmp/DMWeb.config" setAclResourceType="File" setAclAccess="Read,Write" />
</sitemanifest>
In VS 2010, the last line containing DMWeb.config doesn't exist. On top of that, the path to it is wrong. It should be under the App_Data folder.
DMWeb.config is specified in Web.config like this:
<appSettings file="DMWeb.config">
Any help would be greatly appreciated.
This can also happen if there are any files in your project that have been moved, deleted, or renamed from the file system such that Visual Studio doesn't know where to find them.
My error was allmost identical:
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets
(3883): Web deployment task failed. (Object of type 'manifest' and
path
'D:\B\280\Binaries_PublishedWebsites\ProjectName\ProjectName.SourceManifest.xml'
cannot be created. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT.)
The reason I found out is in the ProjectName.SourceManifest.xml file.
There is a line: <appHostConfig path="Default Web Site/ProjectName" />
If this webapp and site does NOT exist on the buildmachine, the error occurs. Once I created a dummy webapp site with the same name on the same site, it built!
And solved by removing that section with MsBuild parameters: /p:IncludeIisSettings=false /p:IncludeAppPool=false (i had those 2 to true, so only applies when you have them true)
Found out that I had an old .wpp.targets file from VS 2010, it was called ~DMWebClient.wpp.targets. In VS 2010, by renaming it, it would ignore it and not apply it. It seems like VS 2013 applies any .wpp.targets files regardless of the file name.
By removing that file, web deploy works again.
Thought I would add as none of the other answers fixed my problem, though perhaps more related to Lightswitch Web Deploy than ASP.NET Web Deploy (though OP doesn't specify which).
There are three projects within a standard Lightswitch Template solution. Two of them might be named lightswitchapp.HTMLClient and lightswitchapp.Server. Neither of these should be deployed! You should deploy the third project lightswitchapp.
I had been getting errors like this, which led me to this page.
Web deployment task failed. (Object of type 'manifest' and path 'manifest xml hidden' cannot be created. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT.)
Great answer above, regarding the Lightswitch Web Deploy...couldn't find anything about it anywhere...kept thinking MS broke this on purpose because they don't want to support LightSwitch anymore...
In any case, once you go through the steps on publishing the main project from the LightSwitch template, a new problem arises, regarding the publish params if you push to a local IIS.
For all of you struggling with that...first install
httpPlatformHandler_amd64.msi
WebDeploy_amd64_en-US.msi
then, make sure "Web Deployment Agent Service" is running as a service
then, in Visual Studio (I am on VS2015 community), on the Publish Settings tab in the wizard, make sure you have something like this:
Service URL:
http://localhost/MSDEPLOYAGENTSERVICE
Site/Application:
Default Web Site\trax01
where trax01 is the name of your web app that runs under Default Web Site (please notice the back-slash before "trax01" compared to the forward-slash in the label for the setting.
Hope it helps somebody else, because this thing ate my liver! :)
The same exception can still happen in Visual Studio 2019. Additional detail for me was Object of type 'manifest' and path 'manifest xml hidden' cannot be created.
In my case the problem was a MsDeployDeclareParameters item in the {ProjectName}.wpp.targets file. It was attempting to set ACL permissions for the downloads folder, but the folder didn't contain any files so it wasn't present in the staging area.
Adding a file to the downloads folder resolved the problem (as would removing the MsDeployDeclareParameters entry from the {ProjectName}.wpp.targets file).
I tried many Solution by updating security to TLS 1.2 (X)
Removed * or special character from variables and password.
But later I found that, we have * in the password of connectionString in web.config.
I changed my password and it started working for me.
<!-- jBoos Configuration ->
<!-- Local -->
mysql configuration
I want to enable both not comment any one of configuration. which configuration is setup depend by windows environment likelinux or windows
Here is one way to do it, sort of manually:
Keep the configuration outside the application war-files.
The project repository contains sample config-files for different needs.
On your machine, or on the server, simply create (or copy from sample) the needed config file.
In spring, read in the config like this:
<context:property-placeholder location="file:/etc/project-name/config.properties"/>
The path /etc/... works on windows also. It points towards c:\etc...
So as you may or may not know, BlazeDS (open source version of LiveCycle Data Services) is a nice way to get your server-side Java and client-side Flex application to play together. Unfortunately, it does have several pitfalls that need to be corrected. I'll try to explain one of them here.
All of BlazeDS's configuration is written via XML files in the flex/ folder of your webapp. The default names are separated for clarity, such as services-config.xml, remoting-config.xml, messaging-config.xml, etc. In these configuration files (particularly services-config.xml), Channels are defined; these setup URIs and objects used to capture and send information between the server and the client. In these config files, it is quite common to use a syntax like so:
<channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel">
<endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
<properties>
<add-no-cache-headers>false</add-no-cache-headers>
</properties>
</channel-definition>
Unfortunately, what they don't tell you is that some of these key-in replacements (ie: {context.root}) are not replaced dynamically upon execution but upon compilation of the WAR file you intend to distribute. Obviously not a good idea when switching domains.
So, instead I seek to dynamically define these channels. According to the documentation, that's all good and fine, but it only works if the channel already exists when the webapp is launched. I feel like that sort of defeats the point.
So my question is, how do you truly create channels dynamically so that both the client and the server recognize their existence?
Read this blog post; I believe it is what you're after.
I believe these xml config files have no direct relation to the server at all. They are used to tell the SWF how to find the server.
During Compile time of your Flex App; the services-config information is, in essence, hard coded into the SWF.