Joe, Just the other day I was helping a friend setup a 'home install' of Remedy, and I was having difficulty trying to get the DB running on 1433, just as you are describing....I went through the configuration, enabled TCPIP, configured it to run on 1433 in all the places I could find, for all of the IP's, etc...couldn't get it to work properly...so, I eventually, dropped to a command prompt, did a netstat -a -n -o, and looked for the process ID of the SQL Server Process, and found what port it was running on, and used that in the installer...
Afterwards, the Remedy service doesn't have issue connecting, because it uses the native client, not the same thing the installer does.... Just a thought for you to get over this hump :) On Sun, Feb 22, 2015 at 6:49 PM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > I did try that yesterday. > > > > It is just too overwhelming with multiple choices that look like they > might mean the same product when choosing the product you are seeking > compatibility information for. And after choosing BMC Remedy IT Service > Management Suite and extracting the Excel file, I got the file that I had > posted in an earlier response which had a URL for a PDF doc having an > address that no longer exists. > > > > Anyway got the PDF file from Laurent who had downloaded it at a time when > that URL had worked. > > > > I’m now facing another issue. > > > > I successfully installed the MS-SQL server 2008, and configured it so that > it’s Management Studio could connect to the server (had some firewall > issues initially where I had to expose port 1433 to inbound connections – > for fun I also exposed the sqlserv.exe for inbound traffic so it would work > even if the SQL port was changed down the line). I’m assuming that is more > than enough to guarantee SQL client connectivity to the SQL server when > running the ITSM stack installer. > > > > > > I tried to connect with the above settings and no problems. I can get into > the SQL server – it’s a one tiered setup for demo purposes. I have my > MS-SQL server installed as a named instance supporting Windows > Authentication. > > > > I then created a ARSystem database, and created an SQL login with windows > authentication [SERVERNAME]\*jmdsouza* and made this Login the dbo of the > ARSystem where [SERERNAME] is the red part of the masked information in the > screenshot. > > > > Subsequently when installing the preconfigured stack installer logged into > Windows as [SERVERNAME]\*jdsouza* (not [SERVERNAME]\*jmdsouza*) for ITSM > 8.1.02, I chose the AR System and the AR Clients as the options for my > installation and at the prompt for the “AR System Server and Database > Information”, I entered the local [SERVERNAME] where all the red masked > info is below. I entered the password of [CAMARO\*jmdosuza*] > > > > > > When I press Next, after a brief while, my next screen I am met with the > error > > > > “TCP/IP connection to the host Camaro2015 using port number 1433 failed. > Possible causes: Database services are not available/running or Network > configuration is not configured correctly for TCP/IP protocol or IP or > host name/ port number is incorrect.” > > > > On my MS-SQL Server Configuration Manager, I have enabled both the Client > and Server TCP/IP protocol.. > > > > What might I be missing? > > > > Cheers > > > > Joe > _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: > "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
