Waiting localhost after set page permission in tutorial

After setting page permissions in tutorial I am getting waiting localhost with spinning circle.
When I run from Visual Stuio Community 2019 I get the below message

Microsoft.AspNetCore.SpaServices:Information: i 「wdm」: Compiled successfully.

Please help me get past this issue.

This is output directly from Radzen
radzen: Generating code ...
radzen: Code generation done in 193ms.
dotnet: info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using 'C:\Users\xxx\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.

dotnet: Hosting environment: Development
Content root path: C:\Users\xxxx\Documents\Radzen\RadzenCRMDB\server
Now listening on: http://[::]:5000
Application started. Press Ctrl+C to shut down.

ng-cli:

ng-cli: ** Angular Live Development Server is listening on 0.0.0.0:8000, open your browser on http://localhost:8000/ **

ng-cli:
Date: 2019-11-06T19:44:47.551Z
Hash: 4dbe3e23bec5b331b6c9
Time: 22117ms
chunk {es2015-polyfills} es2015-polyfills.js, es2015-polyfills.js.map (es2015-polyfills) 285 kB [initial] [rendered]
chunk {main} main.js, main.js.map (main) 493 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 499 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 595 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 6.02 MB [initial] [rendered]

ng-cli: i 「wdm」: Compiled successfully.

radzen: Stopped server.
ng-cli: Exited with code: 1
radzen: Stopped client.
radzen: undefined

It seems that the Angular CLI has crashed for some reason. Check the Access of the Login page. It should be set to Everyone.

Issue resolved.
The problem was that the Login page checkbox was not ticked.

Thanks for your help.

The error is back and I have checked the Login Page.

I am using radzen 2.30.8.

Try upgrading to latest Radzen which is 2.31.1.

I have upgraded to 2.31.2 and still same results

Please see output below...

radzen: Generating code ...
radzen: Code generation done in 214ms.
dotnet: info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using 'C:\Users\hant\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.

dotnet: Hosting environment: Development
Content root path: C:\Users\hant\Documents\Radzen\RadzenCRMDB\server
Now listening on: http://[::]:5000
Application started. Press Ctrl+C to shut down.

ng-cli: ** Angular Live Development Server is listening on 0.0.0.0:8000, open your browser on http://localhost:8000/ **

ng-cli:
Date: 2019-11-11T23:45:31.766Z
Hash: d35bf17687aa7eb9c1d6
Time: 18340ms
chunk {es2015-polyfills} es2015-polyfills.js, es2015-polyfills.js.map (es2015-polyfills) 357 kB [initial] [rendered]
chunk {main} main.js, main.js.map (main) 558 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 577 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 595 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 7.77 MB [initial] [rendered]

ng-cli: i 「wdm」: Compiled successfully.

This log shows a working Radzen application without any problems. What seems to be the problem? You can zip the meta directory of your Radzen app to info@radzen.com and we will troubleshoot.

meta.zip (32.3 KB)

Please see attached meta file

It is the CRM Angular tutorial

There is a JS runtime error which is causing the application to fail. The error is because of a missing $ in of of the template expressions (the first column of the first DataGrid in the Home page):

The correct value for the Template is ${data.Contact.FirstName} ${data.Contact.LastName}

It is working now.

Is there anywhere in the Radzen or Visual Studio where I would have seen an error message for this?

The error message was runtime - it was visible in the browser's developer tools as an invalid Angular template error.