BOXI 3.1 SP5, Pro - just upgraded, so maybe this is related to SP5?
Windows Server 2003 R2.
We are seeing intermittent issues with REFRESH DATE in the lower right corner of a webi report (might be deski too). Refresh date will be far in the past, and even the data is not in line with what is in the db at present -- as though a OLD INSTANCE is being presented for a current instance time.
To reproduce:
1. create new webi report, schedule to run recurring fairly often so many instances build up quickly. (some simple report that won't hurt to run every few minutes). Format as default (this may not matter)
2. after about 60 instances exist, go to history, click on instance time (noting the date/time). Check refresh date in lower right. Several will be correct, but it won't take long before seeing some that are OLD and wrong. Example: instance time says 8/29, open it and refresh date says 8/28.
Checked date/times on servers, no issues there.
Anyone seen this yet, or can reproduce it? Let me know what you think, or if you've gotten a resolution, please!
Have gone into query builder and viewed 'bad instances', however the data for these actually looks OK, so the instance meta data seems intact, but when the instance is retrieved the wrong one seems to be displayed.
Thanks for any input!
Windows Server 2003 R2.
We are seeing intermittent issues with REFRESH DATE in the lower right corner of a webi report (might be deski too). Refresh date will be far in the past, and even the data is not in line with what is in the db at present -- as though a OLD INSTANCE is being presented for a current instance time.
To reproduce:
1. create new webi report, schedule to run recurring fairly often so many instances build up quickly. (some simple report that won't hurt to run every few minutes). Format as default (this may not matter)
2. after about 60 instances exist, go to history, click on instance time (noting the date/time). Check refresh date in lower right. Several will be correct, but it won't take long before seeing some that are OLD and wrong. Example: instance time says 8/29, open it and refresh date says 8/28.
Checked date/times on servers, no issues there.
Anyone seen this yet, or can reproduce it? Let me know what you think, or if you've gotten a resolution, please!
Have gone into query builder and viewed 'bad instances', however the data for these actually looks OK, so the instance meta data seems intact, but when the instance is retrieved the wrong one seems to be displayed.
Thanks for any input!