Skip to main content

Notifications

Announcements

No record found.

Small and medium business | Business Central, N...
Suggested answer

Not able to run business central on new instance on prem

(0) ShareShare
ReportReport
Posted on by 90

I have created new instance on business central from business central administration by opening business central administration then Add instance the new instance is BC190N then i want to use this instance so i tried to create new web server instance  using Administration shell , I used this command 

New-NAVWebServerInstance -WebServerInstance BC190New -Server localhost -ServerInstance BC190N -SiteDeploymentType Subsite -ContainerSiteName "Microsoft Dynamics 365 Business Central Web Client" -WebSitePort 8080 -PublishFolder "C:\BC19.3\WebClient\Microsoft Dynamics NAV\190\Web Client\WebPublish"

but when i try to run business central on tis instance either from IIS or the browser it gives me something went wrong without any details 

Can anyone help me please 

  • Suggested answer
    Inge M. Bruvik Profile Picture
    Inge M. Bruvik 993 Super User 2024 Season 1 on at
    RE: Not able to run business central on new instance on prem

    Do you have any internal firewalls enabled in your network?

  • Ramon C. Profile Picture
    Ramon C. 99 on at
    RE: Not able to run business central on new instance on prem

    hi, i've the same problem. The error in the event log is:

    Problem with comunication protocol between server and client, but the port and all is verified.

    Category: Microsoft.Dynamics.Framework.UI.WebBase.ClientExceptionStateProcessingStrategy

    EventId: 0

    ConnectionId: 0HMN77IVTBVUI

    RequestId: 0HMN77IVTBVUI:00000006

    RequestPath: /BCBS2TEST/SignIn

    ActionId: 4c7d28c0-0c97-4f0b-8ca1-99ba0f223131

    ActionName: Microsoft.Dynamics.Nav.WebClient.Controllers.AuthenticationController.SignIn (Prod.Client.WebCoreApp)

    Mancata corrispondenza del protocollo di comunicazione tra il client e il server.

    Exception:

    Microsoft.Dynamics.Nav.Types.NavConnectionLostException: Mancata corrispondenza del protocollo di comunicazione tra il client e il server.

    ---> System.ServiceModel.ProtocolException: You have tried to create a channel to a service that does not support .Net Framing. It is possible that you are encountering an HTTP endpoint.

    ---> System.IO.InvalidDataException: Expected record type 'PreambleAck', found '72'.

      --- End of inner exception stack trace ---

      at System.ServiceModel.Channels.FramingDecoder.ValidatePreambleAck(FramingRecordType foundType)

      at System.ServiceModel.Channels.ClientDuplexDecoder.Decode(Byte[] bytes, Int32 offset, Int32 size)

      at System.ServiceModel.Channels.ConnectionUpgradeHelper.ValidateUpgradeResponse(Byte[] buffer, Int32 count, ClientFramingDecoder decoder)

      at System.ServiceModel.Channels.ConnectionUpgradeHelper.InitiateUpgradeAsync(StreamUpgradeInitiator upgradeInitiator, OutWrapper`1 connectionWrapper, ClientFramingDecoder decoder, IDefaultCommunicationTimeouts defaultTimeouts, TimeSpan timeout)

      at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreambleAsync(IConnection connection, ArraySegment`1 preamble, TimeSpan timeout)

      at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnectionAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OpenAsyncInternal(TimeSpan timeout)

      at System.Runtime.TaskHelpers.ToApmEnd(IAsyncResult iar)

      at System.ServiceModel.Channels.CommunicationObject.EndOpen(IAsyncResult result)

      at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

    --- End of stack trace from previous location ---

      at System.ServiceModel.Channels.ServiceChannel.OnOpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperationAsync(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)

      at System.Runtime.TaskHelpers.ToApmEnd[TResult](IAsyncResult iar)

      at System.IdentityModel.Selectors.SecurityTokenProvider.EndGetTokenCore(IAsyncResult result)

      at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

    --- End of stack trace from previous location ---

      at System.IdentityModel.Selectors.SecurityTokenProvider.GetTokenAsync(TimeSpan timeout)

      at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OpenAsyncInternal(TimeSpan timeout)

      at System.Runtime.TaskHelpers.WaitForCompletion(Task task)

      at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

      at Microsoft.Dynamics.Nav.Types.Channels.ChunkingDuplexSessionChannel.OnOpen(TimeSpan timeout) in s:\repo\src\Platform\ClientServerShared\Prod.Types\Channels\ChunkingDuplexSessionChannel.cs:line 111

      at System.Runtime.TaskHelpers.CallActionAsync[TArg](Action`1 action, TArg argument)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OpenAsyncInternal(TimeSpan timeout)

      at System.Runtime.TaskHelpers.WaitForCompletion(Task task)

      at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

      at System.Runtime.TaskHelpers.CallActionAsync[TArg](Action`1 action, TArg argument)

      at System.ServiceModel.Channels.ServiceChannel.OnOpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.OpenAsyncInternal(TimeSpan timeout)

      at System.Runtime.TaskHelpers.WaitForCompletion(Task task)

      at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.Open()

      at System.ServiceModel.Channels.ServiceChannelProxy.System.ServiceModel.ICommunicationObject.Open()

      at Microsoft.Dynamics.Nav.Client.ConnectionEstablisher.CallOpenConnection(IAsyncNavService server, ConnectionRequest connectionRequest) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\ConnectionEstablisher.cs:line 464

      at Microsoft.Dynamics.Nav.Client.ConnectionEstablisher.OpenConnection[TChannel](ConnectFailedEventArgs connectFailedArgs, ConnectionRequest connectionRequest, ConnectionOptions connectionOptions, SpnSetting spnSettingToTry, Boolean allowSpnSettingsSwap, UserSettings& userSettings) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\ConnectionEstablisher.cs:line 283

      --- End of inner exception stack trace ---

      at Microsoft.Dynamics.Nav.Client.ConnectionEstablisher.OpenConnection[TChannel](ConnectFailedEventArgs connectFailedArgs, ConnectionRequest connectionRequest, ConnectionOptions connectionOptions, SpnSetting spnSettingToTry, Boolean allowSpnSettingsSwap, UserSettings& userSettings) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\ConnectionEstablisher.cs:line 341

      at Microsoft.Dynamics.Nav.Client.ConnectionEstablisher.OpenConnection[TChannel](ConnectionRequest connectionRequest, ConnectionOptions connectionOptions, UserSettings& userSettings) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\ConnectionEstablisher.cs:line 225

      at Microsoft.Dynamics.Nav.Client.Web.SimpleServerOperation.SimpleServerOperationConnectionEstablisher.OpenConnection[TChannel](ConnectionRequest connectionRequest, ConnectionOptions connectionOptions, UserSettings& userSettings) in s:\repo\src\Platform\Client\Web\Prod.Client.WebCommon\Security\SimpleServerOperation.cs:line 177

      at Microsoft.Dynamics.Nav.Client.Web.SimpleServerOperation.ExecuteCore[TResult,TChannel](RequestContext requestContext, ConnectionOptions serverConnectionOptions, Func`2 operation, Func`3 operationWithContext, Func`2 localExceptionHandler, Int32 retryCount) in s:\repo\src\Platform\Client\Web\Prod.Client.WebCommon\Security\SimpleServerOperation.cs:line 280

  • Suggested answer
    tanya07 Profile Picture
    tanya07 1,548 on at
    RE: Not able to run business central on new instance on prem

    Hi muaz deyab ,

    Can you also check the event log for the same ?

    Thanks,

    Tanya Kharbanda

  • muaz deyab Profile Picture
    muaz deyab 90 on at
    RE: Not able to run business central on new instance on prem

    I tried this link before but still giving the same error

  • muaz deyab Profile Picture
    muaz deyab 90 on at
    RE: Not able to run business central on new instance on prem

    Thanks for your reply ,

    I followed the same process but it still giving the same error , I think the error in the creation of the instance from the administration

  • Suggested answer
    YUN ZHU Profile Picture
    YUN ZHU 75,673 Super User 2024 Season 2 on at
    RE: Not able to run business central on new instance on prem

    Hi, looks like missed some settings, hope the link below can help you.

    https://robertostefanettinavblog.com/2020/03/27/creating-new-instances-of-business-central-web-servers-using-powershell/

    Thanks.

    ZHU

  • Suggested answer
    Tabrez Ajaz Profile Picture
    Tabrez Ajaz 785 on at
    RE: Not able to run business central on new instance on prem

    Hi muaz,

    Please follow this MSDN URL.

    I am sure if you follow the step given you will able to use new instance.

    Don't forget below:
    * Get Access to the WebPublish folder
    * Decide on the site deployment type for the instance [RootSite or SubSite]
    * Run the New-NAVWebServerInstance cmdlet

    If you followed the above steps your new Business Central will run with new Instance.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,661 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,379 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans