First you need to load CSV into class.

After that you can convert objects of your new class into json using SQL JSON_OBJECT function or %ZEN.Auxiliary.altJSONProvider.

You can determine, where does the message comes from by inspecting it's header, get header Id from:

$$$JobCurrentHeaderId

and query Ens.MessageHeader class.

Alternatively, check "process" variable in BPL or current context in ObjectScript processes. Maybe the whole object would be available somewhere.

Check out this list of tools for C#/InterSystems interoperability.

I think you need Caché Managed Provider for .NET.

In <installdir>\dev\dotnet there are several examples available.

Here's an example of accessing properties and array elements:

set jsonObj = [].%FromJSON(filename)
set i = jsonObj.resultSets.%GetIterator()
while i.%GetNext(.key , .resultSet ) {
    set i2 = resultSet.rowSet.%GetIterator()
    write resultSet.name,!
    while i2.%GetNext(.key , .rowSet ) {
        write rowSet.%Get(0),!
    }
}

This error indicates that either login and password are incorrect or that user has insufficient permissions to access management portal.

Generally you'll need to check the service and adapter method lists. Callbachs are often called "On*".

Similar discussion for SQL adapter.

1. Connect to other system via xDBC

2. Query %Dictionary package on a local and remote system and compare results.

You can use %Stream.FileBinary and %Stream.GlobalBinary classes.

Try to replace %XML.String with %String(MAXLEN="");

Try setting Charset to Binary in your BO,  and check that file is Binary in your source BH.

I'd try sending txt file through the pipeline and compare the results.

You may need to either use Selenium or extend production ZEN page.

The ZEN page is EnsPortal.ProductionConfig and host diagram is defined in:

<ownerDraw id="svgDiagram" onrender="zenPage.drawDiagram(zenThis);"/>

And drawn in these methods:

• drawDiagram
• showConnectors
• clearConnectors
   

You can call code from %Installer via Invoke tag (more on that).

To change journaling programmatically execute:

/// Change database journaling state.
/// dbDir - database Directory (can be passed relative to the current working dir)
/// journal - 1 or 0. 1 enables journaling, 0 disables it.
/// zw ##class(util.Test).JournalDB("USER", 1)
ClassMethod JournalDB(dbDir As %String, journal As %Boolean = {$$$YES}) As %Status
{
    quit:((journal<0) || (journal>3)) $$$ERROR($$$GeneralError, "Invalid journal value. 0 or 2 for No, 1 or 3 for Yes")
    set:journal=$$$YES journal=3
    set:journal=$$$NO journal=2

    new $namespace
    set $namespace = "%SYS"
    set db=##Class(SYS.Database).%OpenId(dbDir)
    set db.GlobalJournalState = journal
    quit db.%Save()
}

That said, any particular reason you want unjournaled databases?

Do you catch exceptions?

If not try this:

Try {
 Kill %objlasterror
 Set conn = ##class(%Net.Remote.Gateway).%New()  // No error here
 Set tSC = conn.%Connect("127.0.0.1", "55000", "NETTEST") // No error here
 Write:$$$ISERR(tSC) $System.Status.GetErrorText(tSC),!
 ZWrite %objlasterror 
 Set api = ##class(writetofile.WriteFile).%New(conn) //Here comes the error
 ZWrite %objlasterror 
 Set strFile = "d:\temp\example.txt"
 Set strInput = "Hello world"
 Set ret = api.FilePut(strFile,strInput)
 Set tSC = conn.%Disconnect()
 Write:$$$ISERR(tSC) $System.Status.GetErrorText(tSC)
} Catch ex {
 ZWrite %objlasterror
 Do ex.Log()
 Write ex.DisplayString(),!
}

%objlasterror  can contain more error information. Also check application error log.

Are you on 32 or 64 bits? Check Cache with:

Write $system.Version.Is64Bits()

.Net library should be compiled with the same architecture.