Updated SRM Framework Configuration page according to RN44508 #5756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| This BPA does not generate warnings. | ||
| - The Booking Manager does not have a parameter with name *Logging location*, i.e., element is using a non-supported connector version. To fix re-install the *Skyline Booking Manager* connector that is included in the SRM Solution package and set that version as production. | ||
| - The Booking Manager *Logging location* is not configured, is invalid, does not exist, is not accessible, is part of 'Skyline DataMiner\Documents', or does not end in a backslash character. Not having this configured will make issue investigations more difficult, if not impossible in certain cases. See [SRM Logging Configuration](xref:SRM_logging_config) for more information on how to properly configure logging. | ||
|
|
Member
There was a problem hiding this comment.
Don't we also generate a warning if there are too much log files, or the log folder exceeds a certain size?
Member
Author
There was a problem hiding this comment.
Indeed, added that info
Seppe-Vanhee
approved these changes
Jan 15, 2026
| ### Warning | ||
|
|
||
| This BPA does not generate warnings. | ||
| - The Booking Manager does not have a parameter with name *Logging location*, i.e., element is using a non-supported connector version. To fix re-install the *Skyline Booking Manager* connector that is included in the SRM Solution package and set that version as production. |
Member
There was a problem hiding this comment.
The issues about the logging locations are reported as errors or am I missing something?
Member
Author
There was a problem hiding this comment.
We changed it to warning in https://collaboration.dataminer.services/task/283663
Member
There was a problem hiding this comment.
Then we should probably mention that these were reported as error prior to SRM 2.0.5, I guess.
…as errors in previous SRM versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.