Joe, ITSM requires that the Remedy server be licensed...so, for 'Demo' purposes, if you plan on installing ITSM, you will need to get a Trial license for your server before you can install it...otherwise, you can use the un-licensed Remedy server for evaluation purposes only....the 9.0 Beta License Key is in the forums....which you have access to, so you should be able to find it :)
On Mon, Feb 23, 2015 at 12:20 PM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > Makes sense. So that 2000 entries restriction is only when I actually > start using the system for my demo purposes correct? > > > > I’ve paused without hitting next until I’m able to confirm that. Since I’m > setting this up on my personal PC with the end goal to get onto the version > 9.0 beta test bandwagon, getting a trial license might be a little > complicated for me. > > > > Joe > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *laurent matheo > *Sent:* Monday, February 23, 2015 2:13 PM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Error while setting up my demo instance of AR System and > ITSM Management Suite 8.1.02 on MS-SQL 2008 > > > > Cool ^_^ > > > It should install correctly since it's "just" a database restore when > installing with SSI :) > > > On 23 Feb, 2015,at 07:55 PM, Joe D'Souza <jdso...@shyle.net> wrote: > > Thanks guys, > > > > LJ’s suggestion of checking the actual port the MS-SQL server was using > helped approaching the solution. > > > > The article Laurent forwarded nailed it where it showed where the dynamic > port was set. Had to null that out and set the TCP Port to 1433. > > > > Now the installer is past the error and prompted me for the sa login and > password. > > > > Since I am setting up a demo system, if I leave the license keys blank and > go forward, will it still install the apps with no issues? I understand the > limitations of not being able to insert more than 2000 records etc. as it > used to be in the past. I’m ok with that for this demo instance. > > > > Joe > > > ------------------------------ > > *From: *Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *laurent matheo > *Sent: *Monday, February 23, 2015 1:00 PM > *To: *arslist@ARSLIST.ORG > *Subject: *Re: Error while setting up my demo instance of AR System and > ITSM Management Suite 8.1.02 on MS-SQL 2008 > > > > Btw, are you using the "real" "SQL Server" or the "Express" version? I > just realized that you had "express" in your instance name. > > If it's the Express version it seems you have to setup the 1433 port > manually (which is not the case in the "real / full" SQL Server): > > http://support.webecs.com/kb/a868/how-do-i-configure-sql-server-express-to-allow-remote-tcp-ip-connections-on-port-1433.aspx > > > > > On 23 Feb, 2015,at 06:52 PM, Joe D'Souza <jdso...@shyle.net> wrote: > > LJ, > > > > That is strange. And you might be right on this one. I just ran a netstat > result (hadn’t even thought of that as I had accepted all defaults as far > as ports were concerned during the MS-SQL install) and assumed that 1433 > was the port the SQL server was listening on. It seems its not. > > > > The PID for MS-SQL server is 2056 and this is what I see for that PID on a > netstat. > > > > TCP [::]:49438 [::]:0 LISTENING 2056 > > > > Looks like I might need to use port 49438 for that installer? > > > > If I use that, would I need to reset it back to 1433 anywhere after the > installation? > > > > Joe > > > ------------------------------ > > *From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] On Behalf Of LJ LongWing* > * Sent: Monday, February 23, 2015 10:31 AM* > *To: arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>* > *Subject: Re: Error while setting up my demo instance of AR System and > ITSM Management Suite 8.1.02 on MS-SQL 2008 * > > > > ** > > 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_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > *_ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ * > > _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"
