Empathy List Archives

JK

James Keeline

Fri, Jun 10, 2016 4:35 PM

We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in making a museum clone of the Core Tenant.
I visited the site, logged in as an Administrator, and attempted to create a storage location record. I gave it a Display Name of "Mission Building" and a Name of "Mission." After I clicked "save" I received the following error message at the bottom of the web browser screen.
Connection exceptionCreate request failed: on org.collectionspace.services.location.LocationAuthorityResource csid=

Perhaps this is similar to:
[CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace

| |
| | | | | |
| [CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpaceSteps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2. Click on the Create New tab. 3. Click the Storage Location checkbox and accept the default "Local Storage Locations". 4. |
| |
| View on issues.collectionspace.org | Preview by Yahoo |
| |
| |

This could be an error in my procedure or perhaps a database permissions issue. I did not find in the above a recommended resolution.
I note that Richard is now on vacation so would appreciate anything that would move us towards a solution. Naturally we need this to work to use the system. James D. Keeline

We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in making a museum clone of the Core Tenant. I visited the site, logged in as an Administrator, and attempted to create a storage location record. I gave it a Display Name of "Mission Building" and a Name of "Mission." After I clicked "save" I received the following error message at the bottom of the web browser screen. Connection exceptionCreate request failed: on org.collectionspace.services.location.LocationAuthorityResource csid= Perhaps this is similar to: [CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace | | | | | | | | | [CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpaceSteps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2. Click on the Create New tab. 3. Click the Storage Location checkbox and accept the default "Local Storage Locations". 4. | | | | View on issues.collectionspace.org | Preview by Yahoo | | | | | This could be an error in my procedure or perhaps a database permissions issue. I did not find in the above a recommended resolution. I note that Richard is now on vacation so would appreciate anything that would move us towards a solution. Naturally we need this to work to use the system. James D. Keeline

AR

Aron Roberts

Fri, Jun 10, 2016 5:16 PM

First question: have authorities been initialized in the newly-created
tenant?

If you encounter highly similar error messages trying to create other
authority term records, such as Person or Concept records, that might be
the likely cause. Here's how to initialize those:

https://wiki.collectionspace.org/display/DOC/Initializing+data

On Fri, Jun 10, 2016 at 9:35 AM, James Keeline james@keeline.com wrote:

We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in
making a museum clone of the Core Tenant.

I visited the site, logged in as an Administrator, and attempted to create
a storage location record. I gave it a Display Name of "Mission Building"
and a Name of "Mission." After I clicked "save" I received the following
error message at the bottom of the web browser screen.

Connection exceptionCreate request failed: on
org.collectionspace.services.location.LocationAuthorityResource csid=

Perhaps this is similar to:

[CSPACE-6817] Can't create Storage Location records on
nightly.collectionspace.org - CollectionSpace
https://issues.collectionspace.org/browse/CSPACE-6817

[CSPACE-6817] Can't create Storage Location records on
nightly.collectionspace.org - CollectionSpace
https://issues.collectionspace.org/browse/CSPACE-6817
Steps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2.
Click on the Create New tab. 3. Click the Storage Location checkbox and
accept the default "Local Storage Locations". 4.
View on issues.collectionspace.org
https://issues.collectionspace.org/browse/CSPACE-6817
Preview by Yahoo

This could be an error in my procedure or perhaps a database permissions
issue. I did not find in the above a recommended resolution.

I note that Richard is now on vacation so would appreciate anything that
would move us towards a solution. Naturally we need this to work to use
the system.

James D. Keeline

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

First question: have authorities been initialized in the newly-created tenant? If you encounter highly similar error messages trying to create other authority term records, such as Person or Concept records, that might be the likely cause. Here's how to initialize those: https://wiki.collectionspace.org/display/DOC/Initializing+data On Fri, Jun 10, 2016 at 9:35 AM, James Keeline <james@keeline.com> wrote: > We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in > making a museum clone of the Core Tenant. > > I visited the site, logged in as an Administrator, and attempted to create > a storage location record. I gave it a Display Name of "Mission Building" > and a Name of "Mission." After I clicked "save" I received the following > error message at the bottom of the web browser screen. > > Connection exceptionCreate request failed: on > org.collectionspace.services.location.LocationAuthorityResource csid= > > Perhaps this is similar to: > > [CSPACE-6817] Can't create Storage Location records on > nightly.collectionspace.org - CollectionSpace > <https://issues.collectionspace.org/browse/CSPACE-6817> > > > > > > > [CSPACE-6817] Can't create Storage Location records on > nightly.collectionspace.org - CollectionSpace > <https://issues.collectionspace.org/browse/CSPACE-6817> > Steps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2. > Click on the Create New tab. 3. Click the Storage Location checkbox and > accept the default "Local Storage Locations". 4. > View on issues.collectionspace.org > <https://issues.collectionspace.org/browse/CSPACE-6817> > Preview by Yahoo > > > This could be an error in my procedure or perhaps a database permissions > issue. I did not find in the above a recommended resolution. > > I note that Richard is now on vacation so would appreciate anything that > would move us towards a solution. Naturally we need this to work to use > the system. > > James D. Keeline > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

CH

Chris Hoffman

Fri, Jun 10, 2016 5:23 PM

Hi James,

I’m not sure if this is your problem, but on new systems you need to initialize the default authorities and term lists. Maybe others will remember how to do this. Here’s a note pasted in from the Generic Unix-like or Windows System installation documentation https://wiki.collectionspace.org/display/DOC/Installing+4.3+on+Generic+Unix-like+or+Windows+Systems.

It’s been awhile since I’ve been involved in a new system installation. Maybe you even have to do this for your clone of the core tenant. You could check to see if you are able to create other authorities (e.g., persons). If you can, then I’m sending you down the wrong track.

Chris

Initializing default authorities and term lists
In order to make a newly-created tenant fully functional, you must initialize data for that tenant. The process of initializing data involves reading configuration files in CollectionSpace's Application layer and, from that configuration, creating:
A set of authorities, which will hold authority terms for persons, organizations, storage locations, and the like. Initializing this data is necessary to enable "autocomplete" fields, in which you can type into a field and be presented with suggestions for matching terms.
A set of vocabularies, along with lists of terms in each of these vocabularies. Initializing this data is necessary to populate the options that appear in certain drop down menus.
For instance, when you install a brand-new CollectionSpace system, you'll need to initialize data for the demonstration core and/or lifescitenants. To do so:
Make sure you are logged into the core tenant, then enter this URL in a browser:
http://<ip-address>:8180/collectionspace/tenant/core/authorities/initialise
Make sure you are logged into the lifesci tenant, then enter this URL in a browser:
http://<ip-address>:8180/collectionspace/tenant/lifesci/authorities/initialise
Icon
For Linux, Mac OS X, and other Unix-like systems, there is also a shell script https://raw.github.com/collectionspace/Tools/master/scripts/init-authorities.sh available to automate the process of initializing default authorities and term lists for one or more tenants. You can optionally run that script as an alternative to the manual process described above.

On Jun 10, 2016, at 9:35 AM, James Keeline james@keeline.com wrote:

We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in making a museum clone of the Core Tenant.

I visited the site, logged in as an Administrator, and attempted to create a storage location record. I gave it a Display Name of "Mission Building" and a Name of "Mission." After I clicked "save" I received the following error message at the bottom of the web browser screen.

Connection exceptionCreate request failed: on org.collectionspace.services.location.LocationAuthorityResource csid=

Perhaps this is similar to:

[CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace https://issues.collectionspace.org/browse/CSPACE-6817

[CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace
https://issues.collectionspace.org/browse/CSPACE-6817Steps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2. Click on the Create New tab. 3. Click the Storage Location checkbox and accept the default "Local Storage Locations". 4.
View on issues.collectionspace.org https://issues.collectionspace.org/browse/CSPACE-6817
Preview by Yahoo

This could be an error in my procedure or perhaps a database permissions issue. I did not find in the above a recommended resolution.

I note that Richard is now on vacation so would appreciate anything that would move us towards a solution. Naturally we need this to work to use the system.

James D. Keeline

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi James, I’m not sure if this is your problem, but on new systems you need to initialize the default authorities and term lists. Maybe others will remember how to do this. Here’s a note pasted in from the Generic Unix-like or Windows System installation documentation <https://wiki.collectionspace.org/display/DOC/Installing+4.3+on+Generic+Unix-like+or+Windows+Systems>. It’s been awhile since I’ve been involved in a new system installation. Maybe you even have to do this for your clone of the core tenant. You could check to see if you are able to create other authorities (e.g., persons). If you can, then I’m sending you down the wrong track. Chris > Initializing default authorities and term lists > In order to make a newly-created tenant fully functional, you must initialize data for that tenant. The process of initializing data involves reading configuration files in CollectionSpace's Application layer and, from that configuration, creating: > A set of authorities, which will hold authority terms for persons, organizations, storage locations, and the like. Initializing this data is necessary to enable "autocomplete" fields, in which you can type into a field and be presented with suggestions for matching terms. > A set of vocabularies, along with lists of terms in each of these vocabularies. Initializing this data is necessary to populate the options that appear in certain drop down menus. > For instance, when you install a brand-new CollectionSpace system, you'll need to initialize data for the demonstration core and/or lifescitenants. To do so: > Make sure you are logged into the core tenant, then enter this URL in a browser: > http://<ip-address>:8180/collectionspace/tenant/core/authorities/initialise > Make sure you are logged into the lifesci tenant, then enter this URL in a browser: > http://<ip-address>:8180/collectionspace/tenant/lifesci/authorities/initialise > Icon > For Linux, Mac OS X, and other Unix-like systems, there is also a shell script <https://raw.github.com/collectionspace/Tools/master/scripts/init-authorities.sh> available to automate the process of initializing default authorities and term lists for one or more tenants. You can optionally run that script as an alternative to the manual process described above. > On Jun 10, 2016, at 9:35 AM, James Keeline <james@keeline.com> wrote: > > We have a fresh installation of CSpace 4.2. Our sysadmin succeeded in making a museum clone of the Core Tenant. > > I visited the site, logged in as an Administrator, and attempted to create a storage location record. I gave it a Display Name of "Mission Building" and a Name of "Mission." After I clicked "save" I received the following error message at the bottom of the web browser screen. > > Connection exceptionCreate request failed: on org.collectionspace.services.location.LocationAuthorityResource csid= > > Perhaps this is similar to: > > [CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace <https://issues.collectionspace.org/browse/CSPACE-6817> > > > > > > > [CSPACE-6817] Can't create Storage Location records on nightly.collectionspace.org - CollectionSpace > <https://issues.collectionspace.org/browse/CSPACE-6817>Steps to reproduce: 1. Login as admin on nightly.collectionspace.org. 2. Click on the Create New tab. 3. Click the Storage Location checkbox and accept the default "Local Storage Locations". 4. > View on issues.collectionspace.org <https://issues.collectionspace.org/browse/CSPACE-6817> > Preview by Yahoo > > > This could be an error in my procedure or perhaps a database permissions issue. I did not find in the above a recommended resolution. > > I note that Richard is now on vacation so would appreciate anything that would move us towards a solution. Naturally we need this to work to use the system. > > James D. Keeline > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

talk@lists.collectionspace.org

Attempt to create storage location record generates error