Licence LCI Education
asked on
bad database message after changing the name of a computer
Greetings,
We have a software called IQware that is installed in classroom of our school. It uses a local database configured in Sql management studio 2008.
All the machines of that classroom uses an image created by Acronis and machines are also by default in frozen state using deepfreeze.
That being said, the issue we have is in one of the computer, IQware was not launching at all so I restarted the machine hoping deepfreeze would fix the problem but no luck.
The support team of IQware couldn't help because they don't support SQL so I decided to reimage the machine and once done IQware worked.
After updating the machine and a couple of reboot, IQware was still working. So I renamed the machine and restarted again to apply the change.
After the reboot, I get a message Your database version number UKnown.UKnown.UKnown.UKnow
So I renamed the machine with the name it had after reimaging it and IQware works!!
I am not an SQL expert so I am wondering why changing a name of a machine can give this issue?
I am attaching 3 files:
2 showing that the database is accessible and one with the error message.
Cheers,
Richard
We have a software called IQware that is installed in classroom of our school. It uses a local database configured in Sql management studio 2008.
All the machines of that classroom uses an image created by Acronis and machines are also by default in frozen state using deepfreeze.
That being said, the issue we have is in one of the computer, IQware was not launching at all so I restarted the machine hoping deepfreeze would fix the problem but no luck.
The support team of IQware couldn't help because they don't support SQL so I decided to reimage the machine and once done IQware worked.
After updating the machine and a couple of reboot, IQware was still working. So I renamed the machine and restarted again to apply the change.
After the reboot, I get a message Your database version number UKnown.UKnown.UKnown.UKnow
So I renamed the machine with the name it had after reimaging it and IQware works!!
I am not an SQL expert so I am wondering why changing a name of a machine can give this issue?
I am attaching 3 files:
2 showing that the database is accessible and one with the error message.
Cheers,
Richard
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe SQL permission is set for computer names.
ASKER
Greetings,
I am attaching the files again maybe it's a mistake on my end. Images #2 and #3 shows that the software does connect to it's database. The first screen is the error message.
In my understanding it detects it but won't open it and I believe the suggestion involving the metadata might be the answer.
I'll give it a try and come back to you.
Cheers,
Richard
1.jpg
2.jpg
3.jpg
I am attaching the files again maybe it's a mistake on my end. Images #2 and #3 shows that the software does connect to it's database. The first screen is the error message.
In my understanding it detects it but won't open it and I believe the suggestion involving the metadata might be the answer.
I'll give it a try and come back to you.
Cheers,
Richard
1.jpg
2.jpg
3.jpg
The point being, while you can connect successfully while testing, the question is whether when launched the connection is established.
Without having this app on hand, only the vendor can tell you what the error means.
From a general practice, an error indicating that it can not determine the version which presumably is within a table on the db server, is it can not connect as configured.
Try the use of a hosts file using the old name pointing to the LAN ip
Or update the configuration to point to the new name for the connection.
Without having this app on hand, only the vendor can tell you what the error means.
From a general practice, an error indicating that it can not determine the version which presumably is within a table on the db server, is it can not connect as configured.
Try the use of a hosts file using the old name pointing to the LAN ip
Or update the configuration to point to the new name for the connection.
ASKER
The solution
1: One option edit the c:\windows\system32\driver
Add
127.0.0.1 oldname newname
Provided by Arnold did the trick!!
Thanks a lot!! The ticket can be close
Richard
1: One option edit the c:\windows\system32\driver
Add
127.0.0.1 oldname newname
Provided by Arnold did the trick!!
Thanks a lot!! The ticket can be close
Richard
But guessing your issue is down to how sql stores the server name metadata
https://www.mssqltips.com/sqlservertip/2525/steps-to-change-the-server-name-for-a-sql-server-machine/
Using DNS to call NewServerName OldServerName is another quick workaround