There have been several occasionions where it have been experiences that the Report Viewer and Report Configuration crashes when trying to open.
Double entries in the
dbo.OriginList in SQL database:
At GOE in Egypth there was a child area set up and this caused a problem with two names in the dbo.OriginList in the SQL database.
This had to be edited:
How to fix:
a)
Do a backup and save in a different location!
b) Open SQL Server Management Studio and browse to :
Fls.Qcx.Core.Config -->Tables --> dbo.EntryManager
Right Click and select:
"Select Top 1000 Rows"
Image #1: Entrymanager in SQL database
c) Note down the origin name (see to the right of the table). Keep this origin name - as this is the key to the editing to be done
d) Now open the database:
Fls.Qcx.Core.Historian and open the table:
dbo.OriginList. Here there will most likely be two names in the list and this is causing the problems!
e) Note down the the
OriginListId - which is next to the Origin name noted down previous. This is a so-called GUID which is a unik number, it is enought to note down to be able to seperate the numbers
f) There is a series of databases that needs to be cleaned up (see image #3: the databased marked with a blue line) ! The order of which this is done is not important,
EXCEPT the ”dbo.OriginList” has to be the last one because some of the other files reads of this.
Image #3: List of databases that needs to be edited
g) Right click on one of the marked databases and select:
"Select top 200 rows"
In the example on image #4 below is started with: dbo.EquipmentClasslist. In the table find and select the row which DONT have the same OriginListId as noted down previously.
Image #4: Example of the rows that dont have the correct OriginListId and which have to be deleted.
h)
NOW
find and select the row which DON’T have the same OriginListID as noted down. This row is deleted. A warning will come up: click yes (You are sure you want to delete it). Continue with the other tables which contains OriginListID. Note that some of them have many rows with the possible OriginListId’s.
Delete all the rows which DON’T have the OriginListId you noted now earlier.
Image #5: Example of list with many rows with both right and wrong OriginListId.
Here select and delete the row which don’t have the originListId noted down. Now it is done. It is most likely a good idea to stop and start services, or at least to close and open the workplace.
Hopefully this will solve the problem with the Report viewer and double of samplepoints in sample viewer.