[Progress Communities] [Progress OpenEdge ABL] Forum Post: KB Cause: The exact cause is not known at this time.

Status
Not open for further replies.
D

dbeavon

Guest
I have had a number of support tickets go all the way thru tech support, product development, and get fixed in hotfixes and service packs. But when you go back to review the KB afterwards, it always says " Cause: The exact cause is not known at this time." "The exact cause is not known at this time" site:knowledgebase.progress.com - Google Search Given that the issue is already fixed, it would be very worrisome if they had not found the cause before fixing it! I suspect this part of the KB is never maintained. I would suggest removing it, or moving it to the very bottom where it can be ignored. Usually the " Resolution " part of the ticket is much more important/valuable than the " Cause " part. After scanning hundreds/thousands of articles, I'm fairly tired of reading this "Cause: The exact cause is not known at this time." It is typically just misinformation, and it has no purpose than to trip over. I preceeds the actual resolution, eg. "the fix for this issue is expected to be in the upcoming releases 11.7.x..." Here is an example Progress KB - .Net OpenClient reports exceptions related to concurrent creation of AppObjects.

Continue reading...
 
Status
Not open for further replies.
Top