SQL 2005 Standard & RMS HQ v1.2

Has anyone had any problems getting RMS HQ (v1.2) admin to connect to an RMS HQ Db sitting on SQL 2005 Standard server?. The same HQ Db connected to a SQL

2000 server connects with no problems.

The brand new 2005 sever allows me to use RMS HQ Admin/Manager locally but not on a client PC on the same LAN?

HQ Admin Error says: "To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO)".

The windows firewall feature on the new server is swtiched off and both (TCP) 1433 & (UDP) 1434 Ports are open.

Anybody got any ideas?

Reply to
Bruce Straughan
Loading thread data ...

have you enabled remote connections in SQL 2005??

"Bruce Straughan" wrote in message news: snipped-for-privacy@microsoft.com...

Reply to
root

The problem is you need a little bit of extra software to access the databses on the computer you are getting the error message on. Google SQL management objects and you'll be able to download it. I got the same error message when I tried using SO Administrator on a backoffice computer to access the server. Installing this fixed the problem.

Reply to
jetspeed

I know that some people have posted here that they have used SQL2005 with RMS 1.2, but remember that MS doe NOT support it. RMS 1.3 is the first version to officially support SQL2005...

Glenn Adams Tiber Creek C> Has anyone had any problems getting RMS HQ (v1.2) admin to connect to an RMS

Reply to
Glenn Adams [MVP - Retail Mgmt]

Hi Glen,

Yes I was aware that V1.2 did not support SQL 2005. We will indeed upgrade RMS to V1.3/1.4 in due course but in the meantime we still wish to run V1.2.

I did however manage to resolve the issue by installing the SQL Server 2005 Backward compatibility msi file (located on the SQL Server 2005 install disc

1).

RMS HQ V1.2 can now see our HQ Db running on SQL 2005 server.

Regards Bruce

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Reply to
Bruce Straughan

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.