I'm trying to create build definitions for a project. TFS and build server machines are the same.
When I create the build definition using Default Template (Tfvc Template.12.xaml ), it gives the following error:
Exception Message: The path '$/Scrumproject/Scrumproject/Scrumproject.sln' could not be converted to a local path. Make sure this path is relative to the 'src' folder on the build machine or specify a full server path. (type ArgumentException)
Exception Stack Trace: at Microsoft.TeamFoundation.Build.Activities.Core.LocalPathProvider.GetLocalPath(String incomingPath)
at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
When I use the Upgrade template it gives the following error:
Exception Message: TF42006: The build service could not get the project file for build definition Newdefinition. Ensure the project file exists and the build service account NT AUTHORITY\NETWORK SERVICE is a member of the Build Services group for the team project. (type InvalidBuildTypeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Can anyone help configure the build server correctly?
The first error could be due to an incorrect mapping: is $/Scrumproject/Scrumproject/ folder mapped in the build workspace?
Related
I am trying to set up a build pipeline in Azure DevOPS to build a SSRS project. I have a VSBuild task setup like so
- task: VSBuild#1
inputs:
solution: '$(solution)'
msbuildArgs: '/p:OutDir="bin\Debug" /p:OutputPath="bin\Debug" /verbosity:diagnostic'
configuration: '$(configuration)'
I am getting the following error
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Reporting
Services\Microsoft.ReportingServices.MSBuilder.targets(30,5): Error
MSB4018: The "ReportBuilderTask" task failed unexpectedly
System.ArgumentException: The OutputPath property cannot be blank. It
must provide a relative path that is a child folder under the path of
the report server project. at
Microsoft.ReportingServices.BuildProcess.ReportProjectOptions.GetOutputDirectory()
at
Microsoft.ReportingServices.BuildProcess.ReportProjectOptions.GetOutputFile(String
fileName) at
Microsoft.ReportingServices.BuildProcess.Builder.BuildReport(ReportReportNode
node, ReportProjectOptions options, IMessageHandler messageHandler,
ICheckPublish checkPublish) at
Microsoft.ReportingServices.BuildProcess.Builder.BuildItems(ICollection
collection, ReportProjectOptions options, IMessageHandler
messageHandler, ICheckPublish checkPublish) at
Microsoft.ReportingServices.BuildProcess.ReportBuilderTask.Execute()
at
Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
I checked the PropertyGroup for my configuration and I do see OutputPath, I am also supplying it as an MSBuild parameter additionally, but it isn't getting picked up it seems.
What am I missing? I am using the hosted agent.
As stated in the error message, the path cannot be full path. The azure devops variables carry full absolute paths. I have changed the OutputPath property to carry the relative path and things seem to work now.
I am following the developer guide to deploy SCDF to a minikube cluster on my local machine. Used the helm chart approach. Was able to get it working with the defaults. The default deploys a mariadb in the cluster. I wanted to change it to use an external mysql db that is running in a docker container in my machine (outside the cluster). Followed the recommendations to change the values.yaml to enable the external DB and attributes for external DB connection (URI, dbname, user/pwd etc.).
Then deployed using "helm install my-release -f values.yaml bitnami/spring-cloud-dataflow"
The SCDF pod (& skipper pod) errors out because it can't find the mysql jdbc driver. kubectl logs on the pods show the following error: "java.lang.IllegalStateException: Cannot load driver class: com.mysql.cj.jdbc.Driver"
How do I include the mysql jdbc driver in the image for SCDF that gets deployed (or resolve this problem). I read SCDF already includes the drivers for std databases (true ?). New to helm/k8s so apologies if solution is obvious... Other posts on similar error all talk about including this in the pom.xml . But this is not a dependency issue with my (task) app but SCDF itself.
thanks
-------------------- more detail on the exception stack ---------------
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception; nested exception is java.lang.IllegalStateException: Cannot load driver class: com.mysql.cj.jdbc.Driver
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657)
...
Looks like I just need to specify the mariadb jdbc driver in the values.yaml file for mysql as well. That got past the load class error.
But still would like to know how to prevent class load error for a different driver specified when SCDF is deployed to k8s via the helm chart.
I need help, I was trying to publish my application to production in windows server and i it gave me this error
An error occurred while starting the application.
I runt dotnet command on windows server to check what was the error and this appeared on command line
Unhandled Exception: System.IO.DirectoryNotFoundException:
C:\inetpub\wwwroot\NoPaper_new\wwwroot\files\ at
Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String
root, ExclusionFilters filters) at
NoPaper.Startup.ConfigureServices(IServiceCollection services) in
C:\Users\A0H79224\source\repos\NoPaper\NoPaper\S tartup.cs:line 53
--- End of stack trace from previous location where exception was thrown --- at
Microsoft.AspNetCore.Hosting.ConventionBasedStartup.ConfigureServices(IServiceCollection
services) at
Microsoft.AspNetCore.Hosting.Internal.WebHost.EnsureApplicationServices()
at Microsoft.AspNetCore.Hosting.Internal.WebHost.Initialize() at
Microsoft.AspNetCore.Hosting.WebHostBuilder.Build() at
NoPaper.Program.Main(String[] args) in
C:\Users\A0H79224\source\repos\NoPaper\NoPaper\Program.cs:line 11
basically I have a folder in wwwroot called files which has 3 subfolders where it is possible to upload files to but they are empty.
So i checked the folder in IIS and on wwwroot the files folder doesn't exist.
Why was it not published? How can i solve this problem?
Im trying to connect to a web service using Web Service task. I have used the WsdlFile property to dynamically set the path of WSDL file.
The package executes fine on my local system. When I try to execute the same package on my TEST server ( via Active Batch scheduler), it fails with the following exception :
-1073548540,0x,An error occurred with the following error message: "Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebserviceTaskException: The input Web Services Description Language (WSDL) file is not valid.
I have placed the WSDL file in my TEST server location ( which is equal to the path set in WsdlFile property) and also have Delay Validation = True on WebService task in the package.
Kindly help on how can I resolve this issue.
In my experience this will only occur if the WSDL file is invalid (obviously!) or the SSIS package can't find the WSDL file. Ensure that your configuration exposes the WsdlFile property.
To do so, select SSIS > Package Configurations, and create or edit an existing configuration. Tick the WsdlFile property to expose it:
This will add a property to a configuration file. Ensure that the value of that is set to a full file path e.g. "D:\SSIS\WebService.wsdl"
Finally, once deployed, ensure that your SSIS package references the configuration file you've created.
I was following exact the same steps as described in this article to test the dotnet app.
https://developers.google.com/drive/examples/dotnet
My env is visual studio 2010 and IIS 7
Everything was fine. The app deployment was successful and I could see the login screen and the "allow access" dialog. However once I granted access, I saw the following error.
Can anyone help?
Thanks,
Qiang
Server Error in '/' Application.
Failed to find or load the registered .Net Framework Data Provider.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Configuration.ConfigurationErrorsException: Failed to find or load the registered .Net Framework Data Provider.
Source Error:
Line 82: {
Line 83: StoredCredentialsDBContext db = new StoredCredentialsDBContext();
Line 84: StoredCredentials sc = db.StoredCredentialSet.FirstOrDefault(x => x.UserId == userId);
Line 85: if (sc != null)
Line 86: {
Source File: C:\Qiang\DrEdit\Models\Utils.cs Line: 84
You have to install Microsoft SQL Server Compact 4.0, which is used by the Entity Framework to map model classes into database entities.