1. Support
  2. Knowledge base
  3. 100032459

Unable to copy report output to network folder or redirect locally

Article: 100032459
Last Published: 2016-05-18
Ratings: 0 0
Product(s): Data Insight

Problem

Data Insight may no longer copy report output to a non-default location, such as a network folder, or locally-redirected folder, even after previously functioning properly. It may also stop functioning after a recent install.

When testing different credentials in the redirect section of the report, Data Insight will fail. Clicking  Test Credentials returns "Could not connect to the specified folder."

Error Message

From the Webserver0.0.log:

2016-04-19 00:03:49 INFO:    #{18} [ReportServiceProvider.runCustomScript] Command to be executed: [D:\Program Files\Symantec\DataInsight\\bin\execute.exe, --network, --application, "D:\Program Files\Symantec\DataInsight\\perl\bin\perl.exe", --args, """ -- "" ""D:\Program Files\Symantec\DataInsight\\bin\copynw.pl""  ""D:/DataInsight/data\console\reports\reportruns\3704\outputs"" ""\\FileServer1\DataInsightDailyReports\access_summary_paths\Path Summary\3704"""]
2016-04-19 00:03:49 INFO:    #{18} [ReportServiceProvider.runCustomScript] Command exit code: 18
2016-04-19 00:03:49 INFO:    #{18} [ReportServiceProvider.runCustomScript] Standard output[sdi.execute|domain name:sdi.execute|user name:sdi.execute|password:sdi.execute|start dir:sdi.execute|Success|cusr_token_create|LogonUser|d=DOMAIN|u=DI_Reports, sdi.execute|Success|CreateThread|h=00000000000000BC|thrdid=0x3094, sdi.execute|Success|CreateThread|h=00000000000000C0|thrdid=0x2d5c, sdi.execute|Info|thrdid=0x3094|exit_code=109., sdi.execute|Info|thrdid=0x2d5c|exit_code=109.]
2016-04-19 00:03:49 SEVERE:  #{18} [ReportServiceProvider.runCustomScript] Standard error: [sdi.execute|Failed|cusr_module_execute|CreateProcessWithTokenW|syserr=18, sdi.execute|Failed|redirect|tid=0x3094|ReadFile|syserr=109, sdi.execute|Failed|redirect|tid=0x2d5c|ReadFile|syserr=109]


When redirecting locally, the script may return:

2016-07-27 14:47:52 INFO:    #{18} [ReportServiceProvider.runCustomScript] Standard output[sdi.execute|domain name:sdi.execute|user name:sdi.execute|password:sdi.execute|start dir:sdi.execute|Success|cusr_token_create|LogonUser|d=DOMAIN|u=DI_Reports, sdi.execute|Success|CreateThread|h=00000000000000BC|thrdid=0x108c, sdi.execute|Success|CreateThread|h=00000000000000C0|thrdid=0xec, sdi.execute|Info|thrdid=0xec|exit_code=109.]
2016-07-27 14:47:52 SEVERE:  #{18} [ReportServiceProvider.runCustomScript] Standard error: [sdi.execute|Failed|cusr_module_execute|CreateProcessWithTokenW|syserr=-1073741816, sdi.execute|Failed|redirect|tid=0x108c|ReadFile|syserr=109, sdi.execute|Failed|redirect|tid=0xec|ReadFile|syserr=109]


In these extracts the domain DOMAIN and the user DI_Reports will appear as the credentials that were entered in Data Insight for report redirection.

Cause

Microsoft has released a Security Update to the Secondary Logon Service that prevents Data Insight from authenticating and being authorized to copy report output to the non default location. 

MS16-032: Description of the security update for the Windows Secondary Logon Service: March 8, 2016
http://support.microsoft.com/?kbid=3139914

Solution

There are two workarounds to allow a network copy to function normally, until Microsoft releases a hot fix for this issue.
 
  • Manually copy the report output to the network location after the report is completed
  • Microsoft has provided the following workaround for Veritas Data Insight customers to restore the network copy functionality until a hot fix is released:
              1. Begin by temporarily removing Microsoft Hot Fix KB3139914 from the Data Insight Management Server (MS) and the file server (target) that is hosting the share
              2. Rename C:\Windows\system32\seclogon.dll to C:\Windows\system32\seclogon.dll.orig.

    Note: Windows operating system files are owned by the TrustedInstaller service. The Windows File Protection will prevent any modifications to the files. You will need to first take ownership and edit the CACLS to modify the files.To take ownership of the file, run the following command in a command window that has elevated permissions (right-click, run as administrator) 
    takeown /f C:\Windows\System32\seclogon.dll
                      
                       Edit the CACLS to be able to rename the file: 
    cacls C:\Windows\System32\seclogon.dll /G Administrators:F
                      
                       Now you can rename seclogon.dll to seclogon.dll.orig.

              3. Install KB3139914.
              4. Restore the original seclogon.dll file.
                       Take ownership and edit the CACLS of the new seclogon.dll 
    takeown /f C:\Windows\System32\seclogon.dllcacls C:\Windows\System32\seclogon.dll /G Administrators:F

                       Rename C:\Windows\system32\seclogon.dll to C:\Windows\system32\seclogon.dll.new.
                       Rename C:\Windows\system32\seclogon.dll.orig to C:\Windows\system32\seclogon.dll.

Was this content helpful?

Article Languages