URI Import - Resource Not found

ENV: Windows 2008 R2; TS/LS 7.4.1; OD 7.4.1

We are getting LiveSite Content Services Workflow deployment failures (Err: 5) and from the lcsc.log it appears that the import command is failing and throwing an error message:

uri : Resource not found

08-18-14 @ 15:09:33 [INFO ] URIParserImpl - No alias found for uri:import/
08-18-14 @ 15:09:33 [ERROR] MainController - error.no_such_resource
com.interwoven.wcm.iwrr.core.UnsupportedResourceException: import/

Also getting similar errors for :

08-18-14 @ 16:20:41 [INFO ] URIParserImpl - No alias found for uri Smiley Tongue rojects
08-18-14 @ 16:20:41 [ERROR] MainController - error.no_such_resource

and also "bad request errors" command not specified.

The debug panel does display but does not list any projects. Diagnostics look okay - no obvious errors.

Anyone having success debugging these errors or advice on getting to the root cause I would appreciate it.

Find more posts tagged with

Comments

nipper

That is a hard one. How much customizations have been done ? OOTB PLC ?

If you are not getting the import done, then there will be bo projects. That is expected.

I would first check LiveSiteCSAuth/authoring/etc/deployment/config/lscs-authoring.xml and make certain your branch is defined for the appropriate target (by default development and production - but those could have been changed)

Assuming the error is on the LSCS runtime, I would peruse the lscs.log as well as the idol logs.

HTH

Andy

PNeiswander

Andy, Thanks for the feedback. Everything is pretty much OOTB., We have only installed the lscs_sample app in addition to executing the post-installation steps for the runtime and (lscs authoring). Created a test site in the /default/main/livesitecs/samples branch (which is also configured as the default project).and a few targeting conditions, actions, and rules. Trying to get the test site deployed using the PLC Services deployment is where the errors were getting generated. We using the test site workarea and staging areas for the teamsite-areadiff areas. As near as i can tell the import has never worked.

Using port 8080 we get the debug panel and we don't get errors on queries run through the debug panel, etc ... but of course, no projects so I am not expecting any results. Port 1876 is the lscs runtime port and its active on a tomcat instance, running on the same server as the TeamSite, (tomcat homepage displays) but none of the commands are working. (i.,e. http://ressrvts.ic.aiall:1876/lscs/v1/admin/status returns a 404) (I tried without the v1 also in case that was correct, same answer). I may be doing the status check wrong, I am really not sure if the runtime configuration has a status command; port 8080 responses correctly. We also created a test site The lscs-auth.xml looks correct to me.

The idol logs do not show anything that looks like an errors. The lscs.log is only showing the exceptions that I indicated.

I found one possible error - lscsProps.properties in the LiveSiteCSRT/install/lsdutil/ directory where the LSCSHOME variable was incorrectly set (C: drive instead of E: drive). Not sure how this file plays a role in the import functionality. I restarted runtimes, and ran the iwreset -a after the change - not sure if that was sufficient or not. If anyone knows the possible impact of that error I would appreciate it.

Any thoughts?

nipper

Paul

If you are not seeing admin or debug panel off port 1876 then stop there. LSCS is not installed correctly and it maybe that you are in an unsupported installation.

You said the LSCSRT is on the same instance as LSCSAT. I know you *could* do that in 7.2.1 but I think now that IDOL is taking over I am not certain if that is supported.

You can try to reinstall LSCSRT but I doubt it will help.

PNeiswander

Thanks Andy,

I was afraid it was something like that and we just were not sure if the condition was correctable.

I began setting a second server to act as a runtime server on the possibility that the conflict was in this area. There are a lot of ports to managed when everything is in one location - probably messed something up there.

Thanks for the help..