Forum Discussion

arvinditku3018's avatar
arvinditku3018
Copper Contributor
Sep 04, 2017
Solved

SharePoint framework react-script editor web part error

Hello Everyone

 

I tried to use Sharepoint react script editor web part and received below error.

 

***ERROR MESSAGE: ***Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart). Original error: ***Failed to load entry point from component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart). Original error: Error loading https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1/office-ui-fabric-react as "office-ui-fabric-react" from https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1 Error loading https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1/office-ui-fabric-react Unable to load script https://publiccdn.sharepointonline.com/techmikael.sharepoint.com/11510075fe4212d19d3e6d07c91981263dd697bf111cb1e5f0efb15de0ec08b382cde399/2.34.2/office-ui-fabric-react.bundle.min.js ***CALLSTACK: Error: ***Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart). Original error: ***Failed to load entry point from component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart). Original error: Error loading https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1/office-ui-fabric-react as "office-ui-fabric-react" from https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1 Error loading https://component-id.invalid/3a328f0a-99c4-4b28-95ab-fe0847f657a3_0.0.1/office-ui-fabric-react Unable to load script https://publiccdn.sharepointonline.com/techmikael.sharepoint.com/11510075fe4212d19d3e6d07c91981263dd697bf111cb1e5f0efb15de0ec08b382cde399/2.34.2/office-ui-fabric-react.bundle.min.js at Anonymous function (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:16234:9) at lib$es6$promise$$internal$$tryCatch (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:21064:9) at lib$es6$promise$$internal$$invokeCallback (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:21076:9) at lib$es6$promise$$internal$$publish (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:21047:11) at lib$es6$promise$$internal$$publishRejection (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:20997:7) at lib$es6$promise$asap$$flush (https://localhost:4321/node_modules/@microsoft/sp-loader/dist/sp-loader_en-us.js:20822:9)

 

Any Suggestion?

 

13 Replies

    • Hans Kristian Kristoffersen's avatar
      Hans Kristian Kristoffersen
      Copper Contributor

      Hi Mikael, can this web part be run on SharePoint 2019 on-prem? By on-prem in this case there are no internet connection.

      I get the webpart running on my dev laptop in workbench. But when building a package an deploying it to the on-prem environment. I get a lot of errors on the webpart. Failed to load manifest and so on...

      I'm just starting experimenting with spfx, and trying to implement your webpart in my companys dev environment.

      • Hans Kristian Kristoffersen's avatar
        Hans Kristian Kristoffersen
        Copper Contributor

        The error output is:

        SPLoaderError.loadComponentError]:
        ***Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart).
        Original error: ***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".

        ***INNERERROR:
        ***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".
        ***CALLSTACK:
        Error
        at t._generateErrorStackForIE (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:356:16078)
        at t (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:356:15614)
        at t (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:22166)
        at e.buildErrorWithVerboseLog (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:14402)
        at e.buildLoadComponentError (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:10817)
        at Anonymous function (http://sharepointsite.x.xxx/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:62074)
        at A (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:1743)
        at k (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:1831)
        at Anonymous function (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:5649)
        at h (http://sharepointsite.x.xxx/_layouts/15/next/spclient/10.sp-pages-search.js:8:344)

         

    • Mikael Svenson's avatar
      Mikael Svenson
      Iron Contributor

      Well, it should work just fine loading from the CDN of a different tenant. I’ll do a PR and revert back to local bundling of the fabric. And might upgrade to latest drop as well.

    • arvinditku3018's avatar
      arvinditku3018
      Copper Contributor
      Thanks Wictor. :)

      I noticed that, but later I thought it would be some public cdn so I can access.
      Now it is confirmed. Will give a try again.

Resources