-
Bug
-
Resolution: Fixed
-
High
-
10.120.3, 10.121.1, 10.122.2, 10.124.3
-
None
-
7
-
Severity 2 - Major
-
No
Issue Summary
When expanding PI to the Forecast page and selecting View By Feature, "an error occurs that reports An error occurred on the server while processing the URL."
This is reproducible: (no)
Version: 10.120.3
Steps to Reproduce
- Tier one = Program + PI
- Fo to Forecast page
- Try to expand the PI, the error above
Expected Results
Expand the Forecast PI list as expected
Actual Results
The below exception is thrown -> Evidence from the forecastMainPAge.asp generating error 500 during a POST to "POST /Forecast/ajax/LoadItemData actionType=3&ReleaseID=23&programID=205&EstimationSystem=2"
IIS footprint
2023-06-22 18:17:33 172.22.48.85 POST /Forecast/ajax/ForecastSortReleaseTable ReleaseID=23&ViewBy=3&ViewType=1|210|800a0e78|Operation_is_not_allowed_when_the_object_is_closed. 443 25 172.22.50.21 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10.15;+rv:109.0)+Gecko/20100101+Firefox/114.0 https://JIRAALIGNINSTANCE.jiraalign.com/ForecastMainPage?FirstTime=True&stfilter=true&Programs=205&Releases=23 JIRAALIGNINSTANCE.jiraalign.com 500 0 0 30801
host = PRUSM7WEBF5source = C:\inetpub\logs\LogFiles\W3SVC13\u_ex230622.logsourcetype = ms:iis:auto
ASP Exception Query Timeout
{ [-]
ASP_function: OOFunctionsSql.SetRSParamsCursor
correlationid: RX4w/bsQOqkk+bOL0xnCXCvkeZEFozd2EJmsxD6q8Bk=
customer_db: CUSTOMER
error_description: Query timeout expired
error_id: 13217
error_number: -2147217871
error_source: Microsoft SQL Server Native Client 11.0
log_type: exception
logfrom_location: Website-ASP
sql: EXEC RPM_GET_FORECAST_MASS_UPD_REPORT ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?
timestamp: 2023-06-22T14:17:33.441000-04:00
url: https://JIRAALIGNINSTANCE.jiraalign.com:443/Forecast/ajax/ForecastSortReleaseTable.asp?ReleaseID=23&ViewBy=3&ViewType=1
urlverb: POST
user: 25
version: 10.121.1.31217
}
Show as raw text
host = PRUSM7WEBF5source = c:\log\JIRAALIGN-ASP-20230622.logsourcetype = asp
...
Workaround
Currently, there is no known workaround for this behavior.
- is related to
-
ALIGNSP-19567 Loading...
-
- relates to
-
- resolves
-