logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
scott9677  
#1 Posted : Thursday, September 12, 2019 2:00:45 PM(UTC)
scott9677

Rank: Member

Groups: Registered
Joined: 5/18/2018(UTC)
Posts: 23

Thanks: 2 times
I have recently upgraded from Seal 4.1 to 5.0 and moved the reports from one server to another. I running it in an Azure app service, which has worked well for several versions.

Most of the reports are working great. But some give me this error in the browser:

Sorry, we got an unexpected exception.
Please consult the Windows Event Log on the server machine to have more information...

It seems to be tied to reports that have tabbed views.

The errors center around permissions for either a DLL or web.config. It doesn't say which DLL is missing.

Is there are known issue around this?
epf  
#2 Posted : Thursday, September 12, 2019 3:57:36 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 735
Switzerland

Thanks: 14 times
Was thanked: 135 time(s) in 131 post(s)
Sorry we have still no experience on Azure,
can you check the Repository\Logs, hopefully you will have more information...

I do not see relation between the Tabbed view (in JavaScript world) and missing dll.
thank you for your feedbacks.
scott9677  
#3 Posted : Thursday, September 12, 2019 8:51:11 PM(UTC)
scott9677

Rank: Member

Groups: Registered
Joined: 5/18/2018(UTC)
Posts: 23

Thanks: 2 times
I haven't been able to extract good/useful logging from it:

2019-09-10T18:42:34 PID[5284] Information 09-10 18:42:34 Information: Engine mode: Sampling
2019-09-10T18:42:37 PID[5284] Information 09-10 18:42:37 Information: Application Insights AppId: 054d4010-7481-48a9-9bcf-ffe2e7a2eb5a
2019-09-10T18:42:37 PID[5284] Information 09-10 18:42:37 Information: Press 'Ctrl+C' to exist Application Insights Profiler.
2019-09-10T18:42:37 PID[5284] Information 09-10 18:42:37 Information: Set up shutdown handler.
2019-09-10T18:42:37 PID[5284] Information 09-10 18:42:37 Information: Shutdown handler set to watch D:\local\Temp\JobsShutdown\continuous\ApplicationInsightsProfiler3\s3kswvyv.wbg.
2019-09-10T18:42:37 PID[5284] Information 09-10 18:42:37 Information: Starting main process
2019-09-10T18:42:40 PID[5284] Information 09-10 18:42:40 Critical: Settings have been set from Engine
2019-09-10T18:42:41 PID[5284] Information 09-10 18:42:41 Critical: Settings contract has been updated
2019-09-10T18:42:41 PID[5284] Information 09-10 18:42:41 Critical: Enabled has been set to True
2019-09-10 18:41:22 ~1xxxxxx POST /dev/api/events/wwwroot/longpoll X-ARR-LOG-ID=603ed658-cbe8-47ec-bf94-1be1cada0ecc 443 - 50.251.185.149 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/76.0.3809.132+Safari/537.36 ai_user=Z2rNp|2019-07-18T20:04:15.694Z;+__RequestVerificationToken=27dc5554-478b-4054-b91a-7f2c64354e99;+ARRAffinity=29daffcff19cdb278216dc67909ce2f7ac14dc672c180f39f784c7988656dc3f;+ai_session=dmIOF|1568140128032.395|1568140800941.57 https://xxxxxx.scm.azure...ars%20Transactions2.srex xxxxxx.scm.azurewebsites.net 200 0 0 577 2014 20200
2019-09-10 18:41:30 xxxxxx GET / X-ARR-LOG-ID=daa1b293-ae0d-4dae-810a-378b83f10dc5 80 - ::1 AlwaysOn ARRAffinity=29daffcff19cdb278216dc67909ce2f7ac14dc672c180f39f784c7988656dc3f - xxxxxx.azurewebsites.net 403 503 5 398 707 18181
2019-09-10 18:41:30 xxxxxx GET / X-ARR-LOG-ID=b53dadb5-5406-4845-95c5-eb9d5eb2bf87 80 - ::1 AlwaysOn ARRAffinity=29daffcff19cdb278216dc67909ce2f7ac14dc672c180f39f784c7988656dc3f - xxxxxx.azurewebsites.net 403 503 5 398 707 8419


</head><body><div id="content"><div class="content-container"><h3>HTTP Error 403.503 - Forbidden</h3><h4>You do not have permission to view this directory or page.</h4></div><div class="content-container"><fieldset><h4>Most likely causes:</h4><ul> <li>This is a generic 403 error and means the authenticated user is not authorized to view the page.</li> </ul></fieldset></div><div class="content-container"><fieldset><h4>Things you can try:</h4><ul> <li>Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul></fieldset></div>

That said, I just ran a test with a two tabbed report. I split it into two reports one for each tab and just drug the tabbed subview up and removed the tab view and it worked fine. Either version works correctly using the Windows configuration tool.

Is there a new .net library I need to install?
epf  
#4 Posted : Friday, September 13, 2019 6:23:01 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 735
Switzerland

Thanks: 14 times
Was thanked: 135 time(s) in 131 post(s)
this is the IIS log not the Seal Report log...

the 5.0 version introduces Dashboards and Widget involving new JS library (muury)
<script src='~/Scripts/web-animations.min.js'></script>
<script src='~/Scripts/hammer.min.js'></script>
<script src='~/Scripts/muuri.min.js'></script>
but these are not in the report result, just in the main web site

and we updated the following versions:
Update to Bootstrap 3.4.1, ChartJS library version 2.8.0, Plotly version 1.48.1, JS Tree 3.3.8

So it is mainly JavaScript...according to the error it is more an access right problem..
scott9677  
#5 Posted : Friday, September 13, 2019 1:57:56 PM(UTC)
scott9677

Rank: Member

Groups: Registered
Joined: 5/18/2018(UTC)
Posts: 23

Thanks: 2 times
I'm taking a look at those libraries.

I suspect that it's a missing file and it is just giving an access error as "I can't see this so I probably just don't have access to it".

Well that didn't work.

I think I'm going to try pushing it to a regular server to see if the tabbed reports are still broken or not. I'm pretty sure I'm just missing something small but rather important.
scott9677  
#6 Posted : Monday, September 16, 2019 7:45:28 PM(UTC)
scott9677

Rank: Member

Groups: Registered
Joined: 5/18/2018(UTC)
Posts: 23

Thanks: 2 times
Got a good update. Sorta.

I spun up a new Windows Server 2016 VM, installed the Seal Webserver on it, copied over the Report and Source Repositories over to it and it worked.

I re-copied the files from the second VM up to Azure, and now it works.

Not sure what changed. It's kinda weird. Not a big fan of magical fixes. But it works, so off to other issues.

Thanks for your assistance.

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.