Sp-dev-docs: Server Error in '/' Application when running SPFx WebPart in Chrome

[gonadn]

Expected or Desired Behavior

Open the Workbench.aspx page

Observed Behavior

Server Error in '/' Application
Runtime Error

Steps to Reproduce

gulp serve (Works fine in Edge)

By running gulp serve VS code will open Workbench.aspx in Edge, and in Edge every thing is working fine. But when i click on DEBUG---->Start Debugging , i want my webpart to open in Chrome browser....but i get the "Server Error in '/' Application"

[GrahamMcMynn]

@gonadn - is it possible to include more information or a trace in order for us to help you diagnose the issue?

[gonadn]

Oki, yes but where can i get any trace of what is going wrong...

What iam doing is just to create a simple webpart project, and "gulp serve" to run the solution...
It works fine running on localhost but when i change the URL in serve.json in config folder and run the solution again i get this error:

Iam running it on my Office365 E3 tenant, and the URL is to my test site under developer site....

[gonadn]

I just created a simple SPFx webpart "No Javascript", and run gulp serve....as long as you run it on localhost, the webpart works fine. But if you add URL of the devsite in SPO it give you a server error application....

Something wrong with O365 SPO tenant, update or...?!!

[VidhiGarg]

Hi,
I am also getting the same error in my workbench. The webpart works fine in localhost. The workbench was working fine till yesterday. Not sure if it is because of some update as mentioned by gonadn?

[gonadn]

something is wrong here, i just copy pasted URL from my config.json file into chrome browser and workbench just opened without any error....

But running it from VS Code gives Server Error in '/' Application as i explained above....

[VidhiGarg]

It is working for me as well now. Though I am not sure what made it work. I had just accessed the developer site collection and then tried to access the workbench and it worked.

[phemto5]

I have having the same issues. When i try to get on my tennant workbench i get the same error as @gonadn.
@VidhiGarg What dev site did you go to?

[phemto5]

I had to log on to my tennant on another page (i.e. yourtennant.sharepoint.com ) and then i was Authorized to use the workbench and it started working.

[VidhiGarg]

@phemto5 - Yes, it is an authentication issue. Every time I get this error, even I have to log onto my tenant and then it starts working.

[lucaband]

Super old issue here. Is this still occurring? if yes, can we get actionable logs we can use to investigate or the ability to log in to the system?

[phemto5]

I don't even know i haven't dealt with it in more than a year.

On Tue, Apr 17, 2018 at 1:27 PM, Luca Bandinelli [e-mail]
wrote:

Super old issue here. Is this still occurring? if yes, can we get
actionable logs we can use to investigate or the ability to log in to the
system?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/838#issuecomment-382130694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIDb5WTFADE5T7kl04_1ydtxmfyj9rZks5tplAZgaJpZM4PO7Di
.

--
Nicholas Anderson -
[email protected]

[tsekityam]

I am having this issue currently.

Everything was fine until recent days.

[lennertcc]

Same here since today.

[MNaujoks]

Same error here.

[phemto5]

You need to log on to sharepoint in another window and then the pages will
load.

On Tue, May 29, 2018 at 5:49 AM, MNaujoks [e-mail] wrote:

Same error here.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/838#issuecomment-392763873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIDb0uK2qMLWdCktyVIMa8dNKYE5J26ks5t3UPsgaJpZM4PO7Di
.

--
Nicholas Anderson -
[email protected]

[tsekityam]

Now the case is logged as 11103470 in Micosoft Online Technical Support. I am working with Technical Support Engineer Charlie Guo to resolve this issue.

I will let you know if there is any update on the case.

[jpalo]

Any update @tsekityam?

[tsekityam]

They found the cause of the issue and their PG was starting fixing it, however, no ETA.

Sent from my iPhone

On Aug 31, 2018, at 6:30 PM, jpalo [e-mail] wrote:

Any update?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[andrewconnell]

Is this still an issue? Seems like the latest posting was from late 2018 and was related to an open ticket... if it's still an issue please provide more details about the environment (SPO / SP2016 / SP2018, SPFx version, etc).

[tsekityam]

I opened a premier support ticket #11103470 on this issue. The last message I received from the support team is that PG team was fixing the issue.

I can’t reproduce the issue now. Perhaps PG team did fix the issue.

[andrewconnell]

Cool... seems resolved then since it's old... I'm going to close this issue, but feel free to reopen if I've closed prematurely.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues