Hello all,
When we started the element that is using the skyline booking manager protocol, we got this following quick action errors on:
=> QA2 exception error log when the element was started up
=> flooded or repeated logging of QA330
as shown below.
May we know if there is a way to avoid the logging of QA2 and QA330?
We just feel that the element logging is filled with information that is not useful (especially for QA330).
Thank you for the help.
QA2
2024/01/02 19:39:20.097|SLManagedScripting.exe|ManagedInterop|ERR|0|28|QA2|AfterStartup|Error: System.IO.DirectoryNotFoundException: Could not find a part of the path 'c:\Skyline DataMiner\Documents\Skyline Booking Manager\Configurations'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator`1.CommonInit()
at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetFiles(String path)
at Skyline.DataMiner.Protocol.BookingManager.Settings.UpdateSettingsFileList(SLProtocol protocol)
at QAction.Run(SLProtocol protocol)
QA330
2024/01/02 19:39:31.321|SLManagedScripting.exe|ManagedInterop|DBG|0|28|QA330|RunOnce|Started QAction
2024/01/02 19:39:32.296|SLManagedScripting.exe|ManagedInterop|DBG|0|28|QA330|LateConversion|No Contributing reservations to convert
2024/01/02 19:39:32.296|SLManagedScripting.exe|ManagedInterop|DBG|0|28|QA330|RunOnce|Finished QAction
2024/01/02 19:48:32.551|SLManagedScripting.exe|ManagedInterop|DBG|0|129|QA330|RunOnce|Started QAction
2024/01/02 19:48:32.565|SLManagedScripting.exe|ManagedInterop|DBG|0|129|QA330|LateConversion|No Contributing reservations to convert
Hello Ive,
The protocol version is 2.0.2.61.
As for the installation, I will need to confirm with the customer, as I am doing on behalf.
Hi Min,
Even though it is possible to configure logging levels in general, please take a look at this, in the case of this protocol that won't work because all of these logs are already of the lowest level, no logging level(more details can be found here), meaning they are always logged.
Regarding QA2, since this is an exception I would suggest just creating a folder under specified path even if you don't intend to use it.
Hope this helps,
Cheers
Folder was created to avoid the exception. If there’s a check by default on that, the exception can be avoided as it’s something that needs to be always set.
Regarding the logging I still think it needs a change in qaction 330.. Logging is already on the lowest level at it still shows debug messages
Hi Min,
What version of that protocol are you using?
Did you install the full SRM package or just the protocol?