The user experience is limited because of Java Script of your browser is disabled. Please enable java script and try again to get complete user experience.
The old installation must be completely cleaned up before a new installation. Use the RAIS installer to uninstall the old package. The uninstaller won’t delete the old database from the SQL Server, so if this database is no longer needed, it has to be deleted manually using SQL Server Management Studio. It is always recommended to have a backup of the database before deletion for the case that it contains data which could be needed later.
This error message indicated that asp. Net is not correctly registered with IIS. To fix this, you can run the following command:
aspnet_regiis.exe -i [-enable]
This command is usually located within folder of the installed the. Net framework version (e.g. C:\Windows\Microsoft.NET\Framework\v2.0.50727)
The reason for this could be:
1. The report viewer 2008 not installed.
In this case, install report viewer 2008
2. The report viewer 2008 is installed, but IIS module handler does not recognize it properly.
This is an IIS 7 specific problem when its Handler Mappings does not contain the httpHandler “Reserved.ReportViewerWebControl.axd”.
Solution: In IIS manager, select RAIS web application and then do the following:
- Double-click on Handler Mappings icon in the IIS area
- Click on “Add Managed Handler”
- Enter the following:
• Request path: Reserved.ReportViewerWebControl.axd
• Type: Microsoft.Reporting.WebForms.HttpHandler
• Name: Reserved-ReportViewerWebControl.axd
Since the logging mechanism is bound to the selected record on masks, deleted records could not be seen on the mask itself.
However, they can be seen directly in the database (table: [System - User Operations], field [Operation] = 2) by using SQL Server Management Studio.
Yes you can. You can use the global variable “@SelectedFacility” as parameter in the query.
Upon upgrading the SQL Server 2005 to SQL Server 2008 R2, a new folder tree will be created for the upgraded SQL server, however the “DATA” folder, where databases are kept by default, will be kept inside the original installation folder of SQL Server 2005.
1. Create the “DATA” folder in the folder tree of the upgraded SQL Server 2008 R2, which is by default:
C:\program files\Microsoft SQL Server\MSSQL10_50.XXXX\MSSQL
where XXXX denotes the SQL server name.
2. Check the access permissions to this folder:
• right-click the folder in windows explorer → Properties → Security Tab.
• “SQLServerMSSQLUser” must have full access to the “DATA” folder in SQL Server 2008 R2, and not only “read & execute”.
The [Sources] Field, which is present, for example in Authorization and Inspection, can’t be fully customized from RAIS interface. Currently, customization of this field requires manual operations in the RAIS database using SQL-Server Management Studio.
WARNING: Be sure to have a backup copy of the database before making manual operation in RAIS database. Doing such operations is at your own risk, since mistakes introduced through manual manipulation in the RAIS database could damage parts of the RAIS application. Such operations should only be made by experienced users having deep knowledge in SQL Server and in RAIS structure.
Each [Sources] field in RAIS corresponds to four different entries in a RAIS system table called [RAIS Field]: A parent field having the same name, e.g. “Sources”, and three hidden fields, named usually “sealed”, “unsealed” and “asso”. The parent field, “Sources”, is linked directly to the [Generator] table, while the other three components are linked to the tables [Sealed], [Unsealed] and [Asso], respectively.
For illustration, the steps below demonstrate how to customize the data of sealed sources component in the [Sources] field:
1. Open SQL Server Management Studio and go to the RAIS database.
2. Open the table [RAIS Table] and identify the table, whose [Sources] field you want to customize.
3. Open the table [RAIS Field] and locate the record related to the “sealed” component of the [Sources] Field of concern using the ID of the table identified in step 2.
4. The data which appears in the [Sources] field is controlled through the query whose name is set in the field [Query Name]. Temporarily delete the value of the [Query Name] in order to make that query unassigned, and, consequently, editable in RAIS interface.
5. Now open RAIS 3.2 Web interface and customize this query as described in section 4.5.2 of the document “RAIS 3.1 Web Administrator’s Guide – Part I”.
6. After editing and compiling the query, switch back to SQL Server Management Studio, and re-enter the query name in the field [Query Name] which was deleted in step 4.
That’s it! The sealed component of the [Sources] field will be displayed as customized. Proceed similarly to customize the generator, unsealed and asso components if desired.
This requires table customization from RAIS interface as well as manual operations in RAIS database using SQL Server Management Studio.
Follow the steps described below:
1. Open the tables’ customization mask as described in sections 4.1 and 4.2 of the document “RAIS 3.1 Web Administrator’s Guide – Part I”.
2. Select the table, into which you want to add the [Sources] field and click Edit.
3. Add [Sources] as a multiple lookup field pointing to the table [Generator].
4. Similarly, add three other fields, e.g. [sealed], [unsealed] and [asso], as multiple lookup fields pointing to the tables [Sealed], [Unsealed] and [Asso] respectively. Be sure to uncheck the box “Visible on Forms”.
5. Open SQL Server Management Studio; then go to the RAIS database and open the table [RAIS Field].
6. Locate the records related to the three new fields and set the value of the field [FK Parent Field ID] to the ID of the [Sources] Field which was created in step 3.
Now you would have a [Sources] field in your table/mask.