Server Computer Name case sensitivity problem

(0) Share

Report

Posted on by Muratvzr

743

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.

*This post is locked for comments

All responses (7)

Answers (1)

Verified answer

Muratvzr 743 on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

USE [NAV_18_LIVE]
GO
/****** Object: Trigger [dbo].[Server Instance Upd] Script Date: 13.11.2018 22:02:12 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author: Murat Vezir
-- Create date:
-- Description:
-- =============================================
ALTER TRIGGER [dbo].[Server Instance Upd]
ON [dbo].[Server Instance]
AFTER INSERT,UPDATE
AS
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

END
Community Member Microsoft Employee on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

Hımm realy good solution, can share this code for me. May be i can use some customers.
Muratvzr 743 on at

Like (1)

Report

RE: Server Computer Name case sensitivity problem

Dear Friends,

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.
Stefano Demiliani 37,162 Most Valuable Professional on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

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.
Suggested answer

ShanAbeywicrema 940 on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

Hi Murat,

Instead of server name, Can;t we use IP address ?
Muratvzr 743 on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

Dear Stefano,

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.
Suggested answer

Stefano Demiliani 37,162 Most Valuable Professional on at

Like (0)

Report

RE: Server Computer Name case sensitivity problem

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.