Hello community,
a few days ago we were trying to create a new NAV web server instance linked to a NAV instance as always but suddenly we could not create it. The following error appears:
PS C:\Windows\system32> New-NAVWebServerInstance -ServerInstance $ServerInstance -WebServerInstance $ServerInstance -Server 'localhost'
New-NAVWebServerInstance : Microsoft Dynamics NAV Web Server Components have not been configured for multi-instance.
At line:1 char:1
+ New-NAVWebServerInstance -ServerInstance $ServerInstance -WebServerInstance $Ser ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-NAVWebServerInstance], NavCommandException
+ FullyQualifiedErrorId : WW0082_ADFS,Microsoft.Dynamics.Nav.Management.Cmdlets.NewNavWebServerInstance
We are use to create new NAV web server instances linked to NAV instances all the times through powershell, and we have never had any error.
Do you have any clue about why this error is preventing us to create new web server instances?
Many thanks and regards,
Carlos
*This post is locked for comments
(I got there for an 500 error of my webservice, but its better to answer correctly to this thread)
The first error u was getting, was because u were not admin, so the IDE couldn't load the script.
On the second error u didn't need all the url :
Instead of
-WebServerInstance '"http:/localhost:8080/(..)/Web_Client"
use:
-WebServerInstance "Web Client"
For the main error (of Carlos Herrando
the error was: "Microsoft Dynamics NAV Web Server Components have not been configured for multi-instance."
The problem was the multi-instance on the service. This could be a problem on the ports (same ports for 2 webservices) on NAV SErvice or IIS
It could be the property for multi-tenant in NAV web-service
or another configuration.
Since the reinstalation of NAV resolved the issue, the problem was in the NAV-Service.
I got those errors.
Bro, I'm never used powershell, except to use it as cmd.
Please tell me in a noob way, bro.
The first one, after I click ShowDetais it showed that message
Hi Manish, parameter order is of no importance in shell scripts..
Hello community, finally I solved the problem by repairing NAV installation.
Parameter order is not relevant in PowerShell scripts.
By the way, I have also tested changing the order and the same error appears.
New-NAVWebServerInstance -ServerInstance $ServerInstance -WebServerInstance $ServerInstance -Server 'localhost'
New-NAVWebServerInstance -WebServerInstance $ServerInstance -Server localhost -ServerInstance $ServerInstance
Both script are different,
You have ServerInstance first were as mine is WebServerInstance.
Thank you Manish, I am using the same script and getting the same error.
New-NAVWebServerInstance -WebServerInstance ABC -Server localhost -ServerInstance ABC -ClientServicesCredentialType Windows
We use above to create web services.
Yes, I am running as administrator, and there is not any error when importing the module. The error appears when trying to create the Web Server Instance.
PS C:\Windows\system32> New-NAVWebServerInstance -ServerInstance 'WW0105B' -WebServerInstance 'WW0105B' -Server 'useaddevxq001.us.ead.dev'
New-NAVWebServerInstance : Microsoft Dynamics NAV Web Server Components have not been configured for multi-instance.
At line:1 char:1
+ New-NAVWebServerInstance -ServerInstance 'WW0105B' -WebServerInstance 'WW0105B' ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-NAVWebServerInstance], NavCommandException
+ FullyQualifiedErrorId : WW0105B,Microsoft.Dynamics.Nav.Management.Cmdlets.NewNavWebServerInstance
What error are you getting when you import the module ? are you running it as administrator ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,134 Super User 2024 Season 2
Martin Dráb 229,928 Most Valuable Professional
nmaenpaa 101,156