I have a query that I'm hoping someone can assist me with. Apologies in advance for the lenghty post. Some background:
We are an IT company supporting a client who uses a software package for billing. The database for this software is currently running on an SQL Express 2005 installation and being accessed remotely using a custom port. All users can connect to this database and use the software without any problems from their respective client machines (located remotely to the DB). The connection is established using a FQDN which is mapped to the server's hardware firewall. The firewall then forwards requests on the custom SQL port to the server.
We recently had a complaint from one of the user's regarding a form they are attempting to generate from within the software. The error message they receive is:
"Could not find server GGPBLAID\PIBLAID in sys.servers. Verify that the correct server name was specified . If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers."
I am by no means an expert on SQL Server. I can install and maintain a basic installation and have worked with backups etc but this message means nothing to me. I have done some background reading and attempted to use the procedure referenced (according to the Microsoft website) and although I did not encounter any problems with this, it did not resolve the problem.
I have spoken to the developers of the software and they have assured me that it is not their problem. They mentioned that they could fix it (so it is their problem!) by rewriting sections of the software but this would take a very long time. One of the developers pointed me here:
According to him the problem appears to be related to the period (.) that is used in the FQDN to reference the SQL server. Prior to this remote environment the client worked from a local SQL server and did not experience this issue. The GGPBLAID/PIBLAID mentioned in the error message is the local server name and instance of the server. I am unsure as to why this is being reference as opposed to the FQDN but am assuming that this is part of the problem.
Is this problem resolvable and if so how would I go about doing so?
Any information that someone could provide would be greatly appreciated. The client is in desperate need of having this fixed as soon as possible and, as with most of the third party software we have seen in the past the responsibility has been put on us!
Thanks in advance guys, hope someone can help me out.
Edit: This problem does not occur when running the software in question on the SQL server itself.