Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have this problem earlier in 2017 and now its still occuring.
I am installing NAV 2018 on my computer my computer name is MVEZIR2 my host operating system locale and all language settings are based on Turkish settigs. Everthing works fine but when I try to open page on Development envoirement. It says there is no working instance for this database.
and it collects wrong server name. It thinks my server name is mvezır2 on lower case, but it has to be mvezir2, I change it from server instance table but every time service restarts, It re change it.
I don't think the problem is related to case sensitivity. Do you receive this error when you run a page from Dev Environment? Try to open Dev Environment, go to File --> Database --> Information and verify to have a value in the Server Instance field.
Turkish Accent we have additional letters and its confusing server. Now let me try to explain it with an sample
First you should know we have a letter the sibbling of "i" characther but it hasn't got a point on it. Now
in english language the lower case "i" turns to "I" but in Turkish code page lower case "i" is turns on to "İ" so now in my example
My server name is MVEZIR2 in UPPERCASE
Windows code page is turning it to mvezir2 in lowercase
But now server is turning it to mvezır2 in lower case and windows and all services is not responding this call
This is what is written on my database info page mvezır2.pronic.org:7046/mvnav
This is what should be mvezir2.pronic.org:7046/mvnav
And i cant modify it on any config file it gets automaticy on every server restart.
Instead of server name, Can;t we use IP address ?
Sorry for late response. Not too well understood the problem with the symbols in Turkish language but you can also use the IP address or localhost if you’re working on a local machine. You can also recreate the server instance with a new name.
Thank you very much for your reply, yes i can use ip address for this server name property but it's not classy. I found a solution and I would like to share.
I wrote and update and insert trigger on Server Instance table which is always update wrong turkish characters to right ones.
Hımm realy good solution, can share this code for me. May be i can use some customers.
USE [NAV_18_LIVE]GO/****** Object: Trigger [dbo].[Server Instance Upd] Script Date: 13.11.2018 22:02:12 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGO-- =============================================-- Author: Murat Vezir-- Create date: -- Description: -- =============================================ALTER TRIGGER [dbo].[Server Instance Upd] ON [dbo].[Server Instance] AFTER INSERT,UPDATEAS BEGIN -- SET NOCOUNT ON added to prevent extra result sets from -- interfering with SELECT statements. SET NOCOUNT ON;
UPDATE [Server Instance] SET [Service Name] = cast(UPPER([Service Name])as varchar(250)) COLLATE SQL_Latin1_General_CP1253_CI_AI, [Server Computer Name] = CAST(UPPER([Server Computer Name])as varchar(250)) COLLATE SQL_Latin1_General_CP1253_CI_AI , [Server Instance Name] = CAST(UPPER([Server Instance Name])as varchar(250)) COLLATE SQL_Latin1_General_CP1253_CI_AI -- Insert statements for trigger here
Business Applications communities