Import - Export

<< Click to Display Table of Contents >>

Navigation:  Windows > Core System >

Import - Export

 

Questions and answers about OMNITRACKER Core System ↦ Import - Export:

 

How to handle a scheduled import?

Start an external VB-script in the Scheduled Task. The external VB-script starts a client OtAut-session to the OMNITRACKER server and performs the import:

Set WshShell = CreateObject("WScript.Shell")
WshShell.Run ("c:\MyScript.vbs")

MyScript.vbs:

Set app = CreateObject("OtAut.OtApplication")
Set sess = app.MakeSession ("myhost", 4444, "john", "secret")
Set fld = sess.RequestFolders("MyFolder")
Set objImport = fld.MakeImport()
objImport.Run "MySettings"
...

If .DAT files exist in this path, the E-Mail Gateway will try to send them as soon as the service starts. To prevent the E-Mails from being sent, you can simply delete them or move them to another folder.

 

How to import objects (Configuration Items, CI -details) into the CMDB?

Using the import/export function of OMNITRACKER, the corresponding objects can be imported and exported again. Principally, an import setting must be created for each AI-attribute to be imported. The import source will look like this in minimal version:

Config Item | Value

The attribute is filled via default value, not from the import source. Another possible option is to assign a unique name to the AI-type attribute tuple from the basic data. This name would have to be supplied by the import source. In this case, a single import setting for all attributes would be sufficient. The import source would then have the structure:

Config Item | Type Attribute Tuple Name | Value

For the field Config Item, the identifying fields must also be covered in both variants, since this is a reference field. This is not quite trivial since there are several identifying fields and one of them (in the standard application) is a reference field (Contained in AI), which is often difficult to cover by an import. Therefore, the data import offers the possibility to define a set of temporary identifying fields for the import only. How these fields look is customer-specific (for example, a unique serial number).

For more information, see the OMNITRACKER Administrator Guide: Navigation: User Interface > Data Import and Export > Importing Data into OMNITRACKER.

 

How to execute tasks without charging the OMNITRACKER server?

Start an external VB script in the Scheduled Task:

Set WshShell = CreateObject("WScript.Shell")
WshShell.Run ("C:\MyExternalScript.vbs")

The external VB script starts a client OtAut session to the OMNITRACKER server and executes the export:

Set app = CreateObject("OtAut.OtApplication")
Set Sess = MakeSessionEx(hostname, 5085, "user", "pass", "de")
Set fld = sess.RequestFolders("MyFolder")
Set reqs = fld.Requests
Set tsk = fld.Tasks("MyTask")
tsk.Execute reqs, "c:/MyExport.xls", 3

 

How to fix the following import error? Error creating Excel.Application' object: Error Code: x80070005?

  1. Start/Run DCOMCNFG.EXE
  2. In DCOMCNFG, right click on the "My Computer" ("Arbeitsplatz" in German) and select properties.
  3. Choose the "COM Securities" tab
  4. In "Access Permissions", click "Edit Defaults" and add Network Service or local User Account to it and give it "Allow local access" permission. Do the same for <Machine_name>\Users.
  5. In launch and Activation Permissions, click "Edit Defaults" and add Network Service or local User Account to it and give it "Local launch" and "Local Activation" permission. Do the same for <Machine_name>\Users

 

Tasks: Server side remote execution of MS Office applications (Word, Excel etc.) in a task ends with error: error opening...." ,whereas executing of the tasks manually works fine.

  1. First, the customer must detect if the OMNITRACKER installation turns on 32 or 64 bit
  2. Depending on this he must choose and create the correct folder:
    • C:\Windows\SysWOW64\config\systemprofile\Desktop For 32 bit installations
    • C:\Windows\System32\config\systemprofile\Desktop For 64 bit installations

 

How to handle "Error: Failed to invoke 'Export' on OTCRLib.OTCRReport object: Cannot export report to file '...'?

An export task results in error:

Error 80020009: Failed to invoke 'Export' on OTCRLib.OTCRReport object: Cannot export report to file '...': Exception has been thrown by the target of an invocation. (hr = 0x80131500) (IOtTask).

Reboot the OMNITRACKER application server(s).