While using the OLE DB Source component in SSIS, on updating its SQL Command we started getting the below error for “Phone” column in our Table.
The fix is to open the Advanced Editor for the OLE DB Source component
Change the Data Type (non-unicode string) for the Phone column inside Output Columns in Input and Output Properties Tab.
Changing the Data Type from Unicode string [DT_WSTR] to string [DT_STR] fixed the issue.
Hope it helps..
While trying to publish one of our console application to Azure as Web Job we couldn’t find the “Publish as Azure WebJob..” option
It was because Azure development tools were recently uninstalled from the system.
To install it, go to Windows à Program and Features à Select Visual Studio 2017 and click on Modify.
And select Azure Development for installation
Select Azure Cloud Services tool.
After installation it will ask for restart.
After restart we’d see the option added in our Visual Studio.
Hope it helps.
Recently while writing an SSIS package, we were getting the below exception.
System.Exception: Error: Failed to set field ‘birthdate’ value to ” for entity ‘contact’ (field type: DateTime, value type: String). System.FormatException: String was not recognized as a valid DateTime. (SSIS Integration Toolkit for Microsoft Dynamics 365, v10.2.0.6972 – DtsDebugHost, v14.0.3025.39)
We were getting the exception because the source table was having the birth date field as a string with blank value instead of null and in the destination table we had the corresponding mapped field as DateTime type.
The fix is to add a Derived Column with the following expression, which converts the blank string to null à
“TRIM(ColumnName) == “” ? (DT_STR,4,1252)NULL(DT_STR,4,1252) : Columnname”
Hope it helps..
While trying to call a WCF service from within the C/Al in Microsoft Dynamics NAV, we were getting the below error
“No Action header was found with namespace ‘http://www.w3.org/2005/08/addressing‘ for the given message.”
Strangely enough that request was working properly from within the SOAP UI.
Eventually the following thread came to the rescue
The service was expecting a Soap Header xml containing the Action along with SOAPAction header as shown below within the Soap Envelope.
Hope it helps..
Today for one of our Azure WebJobs when we tried checking its log, we got the below error à
Seemed strange as being the Contributer of that Resource Group, I had access to all other functionality within that resource group.
After much struggle, in one of threads there was a suggestion to try in a different browser or in private browsing mode. And luckily that worked.
Out of all responses, this one makes the most sense for this issue
https://github.com/Azure/azure-functions-ux/issues/2244
Hope it helps..
Recently while developing SSIS packages, the Visual Studio (SSDT) got crashed.
After restarting the Visual Studio and trying to execute the package we got the below error.
System.IO.IOException: The process cannot access the file ‘c:\folder\ssisproject.ispac’ because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder. IncrementalBuildThroughObj(IOutputWindow outputWindow)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.
BuildIncremental(IOutputWindow outputWindow)
ISPAC file is the integration services project deployment file containing the packages and the parameters.
The fix is to open task manager and end the DtsDebugHost.exe task.
DtsDebugHost.exe is the SSIS Debug runtime process that executes the package.
Hope it helps..
Nishant Rana's Weblog 