SQL Server 2014

[anunagarajaiah]

Good Evening,

I am facing a problem with TextPipe filter when invoked by a job in SQL Agent. TextPipe starts processing the file only after a delay of ~30 secs. The job step has only the command to run the filter. I am using /f, /g and /q at the right places in this command. When I run this step, I see that theTextPipe.exe has kicked off (can see this in the Taskmanager) but I do not see the tmp file in the output folder that tells me that the processing has begun. It starts only after ~30secs.

I am using textpipe 9.2.2 AND SQL SERVER 2014.

Can you please help me out here?

Thanks,
Anuradha

[DataMystic Support]

TextPipe 9.2.2 is from September 6, 2012.

You can wade through 4 years worth of release notes here: http://www.datamystic.com/textpipe/whatsnew

Or you could just upgrade and we'd be happy to help.

What type is the file (.zip, docx etc) and is it located on a local drive or network?

[anunagarajaiah]

Thank you for looking into this.

It is a binary file placed in my local folder.

Thanks,
Anuradha

[DataMystic Support]

Sorry, I can't offer specific support for a binary file.

Please upgrade and we'll be happy to help.

[anunagarajaiah]

Thank you. We have upgraded it to 10.0.4. Let me check if this works and will get back to you if the issue persists.

Thanks,
Anuradha

[anunagarajaiah]

The new version has the exit code as -1073741819. Please let me know what this means..

Thanks,
Anuradha

[DataMystic Support]

Thank you Anuradha,

Please send us via email
- filter file (.fll)
- complete command line
- a test file if you can
- Windows versions

[DataMystic Support]

There is no reason for TextPipe 9.9.2 to take 30 seconds to start processing. Delay on exit I can understand, as there is a race condition in MS Help and the only workaround is to pause before exiting.

Are you using SQL Server Agent to start TextPipe? Does it have any dependencies on other tasks? Does the job copy files to another folder before start?

This link may be helpful: https://social.msdn.microsoft.com/Forum ... m=sqltools

It may be due to credential impersonation of the SQL Server Agent proxy.