We have installed DAS 4.1.2 with the CSP14 patch on our NT server DAS. In addition, we have 3 developer’s machines, two of which have the patch installed and one which doesn’t.
We are getting some strange behavior here – on the two machines with the patch installed, we get the message “Document Agents is not online – do you want to send the report anyway” when we attempt to send a report to the DAS. The report does appear in the pending jobs view of the secondary Document Agent and does run, however. A second interesting behavior is that the jobs are scheduled for an hour after the time indicated when we initially schedule the report. That is, if the scheduled time from BO is 10:10, then the job appears and runs at 11:10.
These behaviors do not exist for the one machine without the DAS patch installed. There is no message indicating the DAS is off-line and the time scheduled matches the time requested in BO.
Has anyone experienced these sorts of behaviors? If so, is there a workaround for them?
We have had exactly the same problem although I had put it down to assuming that the NT ‘NetTime’ on the domain that our DAS server is may be different to the time on the domain that our workstations are on (one is a US domain the other a UK - what with daylight and time differences I wasn’t so surprised that the two were out of synch!)
We get the ‘DAS is offline…’ message frequently but I hadn’t put it down to the patch. Have you logged this with Tech Support? All our developer and user machines are running 4.1.2 so I wouldn’t have found the difference that you did.
I haven’t found (or tried to find) a work around yet.
Regards
Jonathan
Project Leader
Global Medical, Regulatory and Product Strategy (GMRPS) IS
We have seen this behavior with V4.1.2, but it seems to be better in 4.1.2a… However we never found a good reason for it!
From: mmalone@CONTEXT.COM[SMTP:mmalone@CONTEXT.COM] Sent: 28 July 1998 17:43
Mike Malone@CONTEXT
07/28/98 09:43 AM
We have installed DAS 4.1.2 with the CSP14 patch on our NT server DAS.
We are getting some strange behavior here – on the two machines with the patch installed, we get the message “Document Agents is not online
– do you want to send the report anyway” when we attempt to send a report to
the DAS. The report does appear in the pending jobs view of the
secondary Document Agent and does run, however. A second interesting behavior
is that the jobs are scheduled for an hour after the time indicated when we initially schedule the report. That is, if the scheduled time from BO
is 10:10, then the job appears and runs at 11:10.
Looks like we have missed something on the latest releases of BO.
What is this patch ‘CSP14’ ?
We installed DAS 4.1.2 as Windows NT service using the executable provide by BO and we faced lot of problems. I mention here some of them :
The DAS could not import a new version of the Universe
from the repository. Whenever there is a new version of the universe exported to the repository, all the jobs on DAS based on this universe fail. The error description was ‘User module failed !’.
Earlier we could publish the refreshed documents over the
network. Now if we choose a directory on the network as the publication directory, we get the same error ‘User module failed !’.
Does the above patch solve these problems or is it for some else. Also how did you obtain this patch ?
The patch is designed to fix the error: ‘Cannot refresh the Document[Command failed Cannot find the ‘xxx’ universe that uses the ‘yyy’ connection . . .’
The patch is available from BusinessObjects technical support.
The patch is designed to fix the error: ‘Cannot refresh the Document[Command failed Cannot find the ‘xxx’ universe that uses the ‘yyy’ connection . . .’
The patch is available from BusinessObjects technical support.
Thanks for the info. We will get in touch with BO technical support to get the patch.
What I have been told by our service provider is…CSP14 is supposed to fix a problem within the updating of the objects.lsi file on DAS. It was not being updated to reflect the universe on DAS hence the error. If you are running scripts and get this error, try running the script on your local machine. If the local run works, try copying your local objects.lsi file to a TEST DAS machine. If it then works on your TEST DAS, you may be a candidate for CSP14 (or 4.1.2a depending where you are).
This problem is due to a corrupted default.ret file in the BO template sub-directory.
To resolve this, create a backup copy of your default.ret (just in case). You can then recreate another default.ret by:
In reporter create a new, simple query, anything will do, and generate a standard report.
Go to Data -> View, select ‘Query 1 with …’ on the left hand window, delete it and all the objects and hit OK. You’ll now have a report with not much info on it, only the “Free Form Report” header. * Re-save as default.ret in your template directory.
Next time you send a report to the DAS, it there will be no error message about it being off-line, and the report will execute at the time specified, rather than one hour later.
Ginny.
______________________________ Forward Header _________________________________
Author: mmalone@CONTEXT.COM at Internet
Date: 28/07/ 0 11:43
…we get the message “Document Agents is not online – do you want to send the report anyway” … the jobs are scheduled for an hour after the time indicated when we initially schedule the report…
Was a solution ever provided for the following problem concerning the DAS being offline when sending a report?
Thanks in advance,
Justin T. Katen
Anheuser-Busch, Inc.
We are getting some strange behavior here – on the two machines with the
patch installed, we get the message “Document Agents is not online – do you want to send the report anyway” when we attempt to send a report to the
DAS. The report does appear in the pending jobs view of the secondary Document Agent and does run, however.