XSW: security error 48s during the XSW load
To resolve the error add a safeguard diskfile-pattern or XOS rule for the XSW collection subvol ($vol.zzxsw*.*) to allow the XSW GUI user to access the collection files.
If the XSW collection subvolume location is $WORK00.ZZXSW*. A Safeguard diskfile-pattern rule might look as follows:
LAST-MODIFIED OWNER STATUS WARNING-MODE
$WORK00.ZZXSW*
* 14OCT20, 10:01 253,1 THAWED OFF
\*.253,001 R,W,E,P,C,O
\*.037.001 R,W,E,P,C
AUDIT-ACCESS-PASS = ALL AUDIT-MANAGE-PASS = NONE
AUDIT-ACCESS-FAIL = ALL AUDIT-MANAGE-FAIL = ALL
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.
Related Articles
XSW: load error ?Cannot open database ''.
Upgrading to an MSSQL supported version of XSW (3.15 or higher) is required. Contact XYPRO for support for more details. If this article did not provide a solution, please open a case with our support team by sending an email message to ...
XSW: XYGATE Compliance PRO (P44), version 2.90 release notes.
RELEASE WARNINGS! * In releases H06.26 and J06.15 of the O/S, the output from the DSAP utility was changed. This will cause data corruption in XSW GUI versions prior to 2.81. This corrupted data could manifest itself in Compliance PRO in a number of ...
XSW: Compliance PRO (P44)Version 2.81 release notes.
RELEASE WARNINGS! * Due to modifications in DSAPDDL for H06.26 and J06.15 O\S versions, collecting Guardian Files on NonStop systems running those versions with XSW versions prior to XSW 2.81 will incur data corruption. This corrupted data could ...
XSW: How to add new XSW users to the XSW SQL server database
To assign a new user to the xsw_role, In SQL server management studio, select: Security logins right-click on the user to be added to the xsw_role properties user mapping then select xsw_role and hit "OK" to save the change. If you are unable to ...
XWG: Error message, "XYPRCHAG: No such file or directory MAF: -1" generated during the load
An XSW collection is started by XYSWSTRT and run as the owner of the file (123,11 in this example). Having different owners for SWCONF and XYSWSTRT is causing unexpected results when a collection is run. SWCONF 101 2048 24MAY2021 9:37 123,255 CUCU 14 ...