We have a 7.5 test server with remote db on SQL Server 2008 x64 on Windows Server 2008 x64, and although we were doing an upgrade from 7.1 and had to host the ARSystem db originally on a local SQL Server 2005 instance (7.1 will not install happily against 2008) for the upgrade install, we did get it moved over to the remote db successfully and have run several of the app installers successfully since the move. That is our ONLY 2008 server so far; everything else is on Windows Server 2003, mostly x64. All of our other SQL Servers are 2005 x64.
You may be having trouble with the 2008 firewall, which is more complex than a Windows Server 2003 firewall to configure. It took us a while to punch a hole in it big enough for ARSystem to connect over port 1433. We had to build three Rules, one Outbound Rule for "SQL Server 1433 Out" Allowing Any connection, and two Inbound Rules, one "SQL Server 1433 In" rule Allowing any local subnet connection, and another "SQL Server 1433 In" rule Blocking Any Public connections to 1433. All of our servers have firewalls turned on. Another very likely possibility is that you don't have the SQL Server connectivity for TCP/IP set up correctly. Make sure that you don't have Dynamic Ports turned on, or that Keep Alive has not been set to a low number (default is 30000), either one of which could have caused the problem you saw in the middle of the installation. Also, I have never seen the requirement you had to specify a port for SQL Management Studio, so you still have some sort of issue with the port on the 2008 box. Microsoft specifically says in the docs that Dynamic Ports do not work well if the firewall is on. Possibly related, I have seen (and have yet to solve) some DCOM issues where the AR Server cannot make the initial connection to the db server after both have rebooted until you first make the connection with SQL Management Studio on the AR Server. In one iteration I had to leave the SQL Management Studio running with an open connection to the SQL Server in order to run a 7.5 installer, but that only happened once. This problem appeared fairly recently, after several rounds of numerous Microsoft security updates. Just a few ideas - we certainly don't have all of the answers on SQL Server connectivity, even in our own environment. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kali Obsum Sent: Tuesday, October 06, 2009 4:18 AM To: arslist@ARSLIST.ORG Subject: Problem installing ARS Server 7.5 on Windows-SQL ** Hi, We're trying to install ARS Server Patch2 on Windows Server 2008 (64-bit) using SQL 2005 (64-bit). App server connects remotely to the DB server. We've tested the ODBC connection from app server to db server and it works. We also tried to login using SQL Management Studio in the app server and we're also able to connect (although in the server name, we had to specify the port number in order to connect; ex: Server Name: Servername\Serverinstance, portnumber). After installation fails, we check the ARSystem db and around 101 tables are created under the db. Content of arerror.log: 390600 : Failure during SQL operation to the database (ARERR 552) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (SQL Server 17) *this is the only content of arerror.log, just repeats this message over and over. Content of arsql.log: <SQL > <TID: 0000002176> <RPC ID: 0000000000> <Queue: Admin > <Client-RPC: 000000 > <USER: > /* Mon Oct 05 2009 16:56:13.4460 */CONNECT ARSystem, USER ARAdmin <SQL > <TID: 0000002176> <RPC ID: 0000000000> <Queue: Admin > <Client-RPC: 000000 > <USER: > /* Mon Oct 05 2009 16:56:30.0740 */*** ERROR *** [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (SQL Server 17) <SQL > <TID: 0000002176> <RPC ID: 0000000000> <Queue: Admin > <Client-RPC: 000000 > <USER: > /* Mon Oct 05 2009 16:56:45.0950 */CLOSE DATABASE Content of arsystem_install_log: Basically, most of the severe errors in the install log are related to service not being found/AR System Server not able to be started. Anyone has any ideas? Regards, Kali NOTICE The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document. We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person. _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
