To resolve this we deployed the same solution as was described in this article. The applications or services that hold your registry file may not function properly afterwards.' after the SAS job say at 1:06AM, and then if during your job execution you call the Oracle Bulkloader.exe prior to the end of the SAS.exe you would get the 'No Application is Associated.' error and the proc append would fail. The events would have to occur in this order for this to happen.

The error specifically occurs when a SAS.exe process has started say at 1:04AM, then a Windows Event 1530 occurs 'Windows detected your registry file is still in use by other applications or services. We only encounter this error when a program is running under job scheduler execution, many dozens if not a hundred jobs are run daily on multiple SAS systems. All of out SAS programs are executed via batch files under control of 'Maestro' by Tivoli a job scheduler. We believe we have now solved this issue with a change to Group Policy. It did impact things in a subtle enough way to avoid this issue for a period of time (just due to the timing of things). NOTE: PROCEDURE APPEND used (Total process time):įollow up - The fix described above was NOT the ultimate solution to this issue. NOTE: Statements not processed because of errors noted above. We have been to SAS support numerous times throughout years, yet this issue persists, unresolved, I would be curious to know if anyone else has encountered this or a similar issue or solution? Given the two conditions above if we were to attempt a PROC append and use the bulk loader options which invoke SQLLDR, and it was 5 minutes after the hour, we would likely encounter a 'No application is associated with the specified operation' error. As a side note, these are the only conditions we have ever seen this error, also we run many bulk loads via proc append that do not fail, because they do not run during those particular timeframes. It only happens when we perform an Oracle bulk load via a proc append function which transfers control to SQLLDR.exe and creates a dat, log and ctl file, the error occurs prior to actually beginning the load.ģ.

The error is intermittent, it does occur within the first 5 minutes or so of an hour nearly exclusively, though we haveĪlso seen it occur up to five minutes after the half hour too, say 8:35.Ģ. We see it intermittently but with some interesting factors ġ. No application is associated with the specified file for this operation.

We are running SAS 9.3 on a Windows Server

No file associated with this program