Patrick, The service is running fine. No errors appear in the log.
Mark From: [email protected] [mailto:[email protected]] On Behalf Of Galligan, Patrick Sent: Thursday, February 02, 2017 2:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser Mark, Can you check what the Archivesspace.out log is saying when you run the service? Even if it never starts up ArchivesSpace, it should give you an error message saying what's going on. -Patrick Galligan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mark Bliese Sent: Thursday, February 02, 2017 1:02 PM To: Archivesspace Users Group <[email protected]<mailto:[email protected]>> Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser Dear Ben, Thank you for taking the time do discuss this. I have ASpace loaded on a Windows Server 2008 R2. This has been in place for a number of years. Before I installed the Windows service and the changes necessary to run against MySQL, I ran it against the demo database. No problems accessing that. I am checking with another vendor of ours where their app uses MySQL and Java to make sure that any changes I make don't cripple their app. There is only one system variable that I left alone because of that. Once I hear back from them, I can make a change and see if that allows me access. To answer your question about the firewall, I have checked that and it is ok. I have tried a browser both on the server and on a client to see if I can access the database. Mark From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ben Finberg Sent: Thursday, February 02, 2017 11:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser So although I'm not an ArchivesSpace expert (like, at ALL), I'm pretty decent at general computer troubleshooting. The fact that you couldn't run ArchivesSpace using the foreground batch file eliminates the Windows service as the culprit, so we're at least making a little progress. A few initial thoughts/questions I have at this point: * What version of Windows are you running? Is it a dedicated PC for ArchivesSpace or is it running other services too? Is it a new Windows install or has it been around for a while? * As an experiment, have you tried totally disabling your Windows firewall(s), for all networks? Do you have 3rd party antivirus protection that might have a built-in firewall that's blocking the ArchivesSpace ports? Have you tried browsing both from a browser on the ArchivesSpace PC (to http://localhost:8081) and from another computer (to http://aspacePCname:8081)? * There was a thread on this newsgroup yesterday that mentioned an issue with multiple versions of Java causing a conflict. Take a peek in C:\Program Files (x86)\Java...do you see multiple jrexxx folders in there? Benjamin Finberg, Director of IT and Operations The Georgia O'Keeffe Museum 505.946.1057 217 Johnson St., Santa Fe, NM 87501 www.okeeffemuseum.org<http://www.okeeffemuseum.org/> A Great American Artist, a Great American Story. Explore the remarkable career of Georgia O'Keeffe through her artwork, the objects and places that were meaningful to her, and the experiences that defined her life. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mark Bliese Sent: Thursday, February 2, 2017 10:00 AM To: Archivesspace Users Group <[email protected]<mailto:[email protected]>> Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser Yes, I am running Windows. I stopped the Windows Service, then launched the ArchivesSpace.bat file I then tried to access the app in the browser. Still no go. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ben Finberg Sent: Thursday, February 02, 2017 10:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ASpace not accessible using browser Are you trying run it on Windows? If so, did you try launching it in the foreground, running ArchivesSpace.bat? This is a good first step in trying to isolate where things aren't working. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mark Bliese Sent: Thursday, February 2, 2017 8:46 AM To: [email protected]<mailto:[email protected]> Subject: [Archivesspace_Users_Group] ASpace not accessible using browser I have installed ASpace, set up the service and database using the instructions. Service is running, ports have been added to the firewall for inbound access. I am not able to connect to ASpace from a client browser or from a browser on the server. There has to be a way to troubleshoot this, so if anyone has suggestions I would appreciate some assistance. Mark J. Bliese IT & Research Concordia Historical Institute 804 Seminary Place Saint Louis, MO 63105 Ph: 314-505-7907 Fax: 314-505-7901 [email protected]<mailto:[email protected]> http://concordiahistoricalinstitute.org [cid:[email protected]] Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance. Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance. Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance. Confidentiality Notice: This e-mail message, including any attachments, originates from Concordia Historical Institute of The Lutheran Church-Missouri Synod. It contains information which may be confidential or privileged, and is therefore restricted to and for the sole use of the intended recipient(s). If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, copying or printing of this e-mail is strictly prohibited. This e-mail is the sole property of Concordia Historical Institute and may not be distributed by any means without this disclaimer. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and delete the message from your computer and network systems. Please accept our thanks, in advance.
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
