Hello CSpacers,

I downloaded the 1.7 tarball today and went about setting it up, but
have run into a snag.

I'm following the steps in
http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
including the ant create_db import, so my assumption is that nothing
lying around from previous installations on the server should be
interfering. Correct?

The first sign of something possibly being off is this error in
server.log, which shows up when logging in to the web UI.

https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

Perhaps this has to do with not having initialized the authorities?

Moving on, I tried to initialize the authorities, and got the error

"Create request failed:  detail:

org.collectionspace.services.common.document.DocumentException:
org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
found: uri".

More details:

https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
to localhost, but just to be sure I changed it to the server's IP,
restarted, and tried again -- same results. That segment looks like:

 <persistence>
      <service>
          <url>http://our ip:8180/cspace-services</url>
    <config-tenant></config-tenant>
    <config-bindings></config-bindings>
    <ims-url>http://our ip:8180/collectionspace/chain/</ims-url>

      </service>
  </persistence>

Since that fails, of course the controlled list dropdowns are all unpopulated.

I assume I'm missing something obvious, but sadly it isn't obvious to
me. Any ideas?

thanks,
Joe

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

Hello CSpacers,

I downloaded the 1.7 tarball today and went about setting it up, but
have run into a snag.

I'm following the steps in
http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
including the ant create_db import, so my assumption is that nothing
lying around from previous installations on the server should be
interfering. Correct?

The first sign of something possibly being off is this error in
server.log, which shows up when logging in to the web UI.

https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

Perhaps this has to do with not having initialized the authorities?

Moving on, I tried to initialize the authorities, and got the error

"Create request failed:  detail:

org.collectionspace.services.common.document.DocumentException:
org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
found: uri".

More details:

https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
to localhost, but just to be sure I changed it to the server's IP,
restarted, and tried again -- same results. That segment looks like:

 <persistence>
      <service>
          <url>http://our ip:8180/cspace-services</url>
    <config-tenant></config-tenant>
    <config-bindings></config-bindings>
    <ims-url>http://our ip:8180/collectionspace/chain/</ims-url>

      </service>
  </persistence>

Since that fails, of course the controlled list dropdowns are all unpopulated.

I assume I'm missing something obvious, but sadly it isn't obvious to
me. Any ideas?

thanks,
Joe

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

At first glance that looks like an error in the setting up of the service
layer, not an error with initializing anything - if you log into your
database and look at the tables do they appear to have the structure you
would expect. You are right that the ant create_db import effectively
destroys all your data and recreates the database structure inline with

new service layer xsd's and xmls.

So I would first check that it has initialized the "groups" Table within

nuxeo db.
In the first server log yo sent it suggests that the services has not
correctly initialized the Group Procedure. Patrick ought to be able to

you in any problems with that as that was a service I believe he added I
believe.

the second error:

Property not found: uri

suggests a mismatch between the schema described in cspace-config.xml and
the internal service schema. Tho uri isn't a field I would expect in a
payload to create an vocabulary unless you are creating an authority with
relationships. However, because of the earlier issue with the service

I believe if you remove the earlier issue then the later issue might
magically disappear if it is a mismatch.

Good luck

Chris

Hi Joe,

I just attempted replicating your issue but wasn't able to.

I followed the install instructions on a Debian 5 machine on top of a
cspace 1.6 Installation. I did not delete or remove anything from the old
installation, and used the settings.xml file like you.

Two trouble shooting suggestions:

- Make sure there is no "local-settings.xml" present .. if there is,
this will be read instead of the newer "settings.xml".
- Make sure the 'ant import' script ran without errors (obvious as this
may seems, there is a tendency of missing this - me included)

Will let the brainier parts of the cspace team come up with more
suggestions!

~Kasper

On 06/01/2011 06:37 PM, Joe Slag wrote:

Hello CSpacers,

I downloaded the 1.7 tarball today and went about setting it up, but
have run into a snag.

I'm following the steps inhttp://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
including the ant create_db import, so my assumption is that nothing
lying around from previous installations on the server should be
interfering. Correct?

The first sign of something possibly being off is this error in
server.log, which shows up when logging in to the web UI.

https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

Perhaps this has to do with not having initialized the authorities?

Moving on, I tried to initialize the authorities, and got the error

"Create request failed:  detail:
org.collectionspace.services.common.document.DocumentException:
org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
found: uri".

More details:

https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
to localhost, but just to be sure I changed it to the server's IP,
restarted, and tried again -- same results. That segment looks like:

<persistence>
     <service>
         <url>http://our ip:8180/cspace-services</url>
   <config-tenant></config-tenant>
   <config-bindings></config-bindings>
   <ims-url>http://our ip:8180/collectionspace/chain/

Since that fails, of course the controlled list dropdowns are all unpopulated.

I assume I'm missing something obvious, but sadly it isn't obvious to
me. Any ideas?

thanks,
Joe

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

Talk mailing list
Talk@lists.collectionspace.org

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

At first glance that looks like an error in the setting up of the service
layer, not an error with initializing anything - if you log into your
database and look at the tables do they appear to have the structure you
would expect. You are right that the ant create_db import effectively
destroys all your data and recreates the database structure inline with

new service layer xsd's and xmls.

So I would first check that it has initialized the "groups" Table within

nuxeo db.
In the first server log yo sent it suggests that the services has not
correctly initialized the Group Procedure. Patrick ought to be able to

you in any problems with that as that was a service I believe he added I
believe.

the second error:

Property not found: uri

suggests a mismatch between the schema described in cspace-config.xml and
the internal service schema. Tho uri isn't a field I would expect in a
payload to create an vocabulary unless you are creating an authority with
relationships. However, because of the earlier issue with the service

I believe if you remove the earlier issue then the later issue might
magically disappear if it is a mismatch.

Good luck

Chris

At first glance that looks like an error in the setting up of the service
layer, not an error with initializing anything - if you log into your
database and look at the tables do they appear to have the structure you
would expect. You are right that the ant create_db import effectively
destroys all your data and recreates the database structure inline with

new service layer xsd's and xmls.

So I would first check that it has initialized the "groups" Table within

nuxeo db.
In the first server log yo sent it suggests that the services has not
correctly initialized the Group Procedure. Patrick ought to be able to

you in any problems with that as that was a service I believe he added I
believe.

the second error:

Property not found: uri

suggests a mismatch between the schema described in cspace-config.xml and
the internal service schema. Tho uri isn't a field I would expect in a
payload to create an vocabulary unless you are creating an authority with
relationships. However, because of the earlier issue with the service

I believe if you remove the earlier issue then the later issue might
magically disappear if it is a mismatch.

Good luck

Chris