I am upgrading our b2b website to 6.7 hybris version. We have copied the config and custom folders to new 6.7 setup. We have also copied the data and media. Updated the system.
After server startup the entire WCMS section is not rendering due to which the components on home page do not open. It gives me the below error on console
**WARN [hybrisHTTP37] [DefaultCMSComponentRendererRegistry] Error processing component tag. currentComponent [TKNavigationBarComponentModel (8796148630588#1)] exception: Missing extension info for given extension name
Dec 30, 2019 11:12:31 AM org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet [DispatcherServlet] threw exception
java.lang.NullPointerException: Missing extension info for given extension name
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:805)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$DefaultExtensionAccessor.getInfo(AcceleratorAddOnFilter.java:272)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$DefaultExtensionAccessor.getExtensionDir(AcceleratorAddOnFilter.java:267)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$ResourceAddOnResolver.getExtensionPath(AcceleratorAddOnFilter.java:113)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter$ExecutableResourceAddOnResolver.getAddOnFullPathName(AcceleratorAddOnFilter.java:160)
at com.thyssenkrupp.b2b.global.baseshop.storefront.filters.AcceleratorAddOnFilter.doFilter(AcceleratorAddOnFilter.java:61)**
The localextensions.xml is same as 6.4 version. We have also tried querying tables to check if CMSNavigationNodes are present in the DB . In backoffice to the WCMS node is missing.
Can you please suggest what could have gone wrong here ?
There are documentation for upgrading. You need a lot of work for every version. For example check 6.6 to 6.7 guide (This link private, you need account on SAP).
I was able to fix this using
https://answers.sap.com/questions/12766398/missing-extension-info-for-given-extension-name.html
I had to manually change the Resolver file in my custom storefront extension as it was a copy of 6.4 and had the bug mentioned in the above link.
Related
I took over a website for my client and I tried adding an extension to Typo3. When I did, the whole website crashed and displays a HTTP ERROR 500. I found this thread with a similar problem, followed the instructions and erased the key that was supposed to be removed typo3 site offline after extension upload but that didn't work.
I gained access to the cPanel since I couldn't access the backend login page. So now i'm able to access all of the root files and hopefully fix the problem. Does anyone know anything to fix it?
You should read the error log (for the PHP service or Apache, depending on how your hosting works). There you can see the actual error message which then can give you an indication what's actually wrong.
The most common reasons are:
Extension version is not compatible with the version of TYPO3 you used (and you ignored the warning when installing).
Extension is written in a way that it assumes you update the database schema, which may not happen automatically when you install the extension.
Extension calls on classes that must be loaded and does not provide class loading for the installation you use (e.g. some extensions only offer composer support and won't work if you install without composer).
Extension uses PHP modules that are not installed or is incompatible with the version of PHP that is used.
You should be able to recover this by using the TYPO3 install tool to manually update the database schema and perform checks that the extension works (TYPO3 8.7+ only). If that does not help we will need additional information:
Which TYPO3 version do you use?
Was it installed with composer?
What is the exact error message you get in PHP error logs?
If the extension you installed is public, a link to it would help determine why you get the error.
Hope this helps!
My colleague has developed an extension project to Approve Purchase Contract application using local trial Web IDE. I imported his project using the licensed Web IDE from SAP gateway server. The folder structure looks like this:
.
My index.html looks like this:
.
Whenever I run using index.html or Component.js, I'm getting below error. Kindly help.
Uncaught Error: failed to load
'ui/s2p/mm/purcontract/approve/MM_PC_APVExtension/Component.js' from
./Component.js: Error: failed to load
'ui/s2p/mm/purcontract/approve/Component.js' from
/sap/bc/ui5_ui5/sap/MM_PC_APV/Component.js: 404 - Not Found
The error message says:
ui/s2p/mm/purcontract/approve/MM_PC_APVExtension/Component.js is found but it can not be loaded because a dependency is not found. That missing dependency is ui/s2p/mm/purcontract/approve/Component.js which should be available at /sap/bc/ui5_ui5/sap/MM_PC_APV/Component.js.
Please follow the SAP Documentation DOC-58342 step 4.2 to be sure the "Approve Purchase Contract App" is installed and activated and the necessary roles are assigned.
Thanks schnoedel. I resolved the issue by recreating the extension project and copying the code changes from old project.
I am migrating an existing app from teiid-8.8.1c1/jboss-as-7.2.0 to WildFly 9.0.2
Teiid 8.13.4. I have been able to update dependencies in all cases except one:
I have one class getting an Admin instance from org.teiid.adminapi.AdminFactory as follows:
AdminFactory.getInstance().createAdmin(...)
So that is can get and check status on a VDB.
But is seems that the AdminFactory is no longer part the teidd adminapi. Is there some new way to get an admin instance?
Per teiid message board, it was moved to teiid-jboss-admin jar:
[TEIID-3503] Development with Embedded teiid should not require dependency on EAP - JBoss Issue Tracker separated out the EAP dependent Admin functionality into the teiid-jboss-admin jar. It doesn't look like that was called out in the release notes or a specific migration doc, so I'll make sure that gets updated.
I'm recently going through my first Kentico upgrade on a site that was previously handed to me from somebody else. There were some hinks initially, but I have to say the V8.2 to V9.0 upgrade is gone off with a degree of success. There is one last issue I'm tackling. Initially the issue was with images stored in the database, but I resolved that with setting custom URL extensions. The style sheet we have in the database is returning a 404, so the entire site is without style.
I did some digging, and found the following:
While we were using ~/CMSPages/GetCSS.aspx in V8.2, that appears to have been deprecated/obsolete for some time now. The CSS references in the master page all point to ~/CMSPages/GetCSS.aspx.
In V8.2, I can confirm the presence of ~/CMSPages/GetResource.ashx, but that appears to be missing after the V9.0 upgrade. I installed a blank template site as well to confirm, and it's not there either. I verified I am using the latest upgrade package. I had already hit an issue with the pre-12/15 edition.
The V8.2 ~/CMSPages/GetResource.ashx does not work in a V9.0 as the API for CMS.UIControls no longer contains the ResourceHandler class (which is also used in ~/CMSPages/GetCSS.aspx).
I can confirm in the V8.2 codebase that ~/CMSPages/GetResource.ashx works, returning the specified stylesheet.
TL;DR - Upgrading from V8.2 to V9.0, I appear to be missing ~/CMSPages/GetResource.ashx, and am not sure where it got off to.
Environment Information
Test Server: Windows Server 2008R2 SP1 on IIS 7.5 w/ .NET 4.5.2, MSSQL 2008R2 Database backend
Dev Server: Windows 8.1 with IIS 8.5, VS 2015 and MSSQL 2008R2
Kentico V8.2 Site in Portal Mode
I appreciate any ideas you have.
Thanks!
Most of the .ashx were moved to the CMS.UIControls assembly and adjusted to implement IHttpHandler.
This way the handlers can be used by any application that references the Kentico libraries, specifically the UIControls. This approach has been utilized e.g. in the new MVC support in Kentico 9.
If you need to customize the handlers you can take advantage of the GetFileHandler and AdvancedGetFileHandler abstract classes implementing IHttpHandler.
I was receiving a 404 on GetResource.ashx in v8 when deploying my site. I have my site setup as a web application. My problem was I was only deploying CMSApp using Visual Studio. I needed to also deploy CMSApp_AppCode. https://docs.kentico.com/display/K81/Publishing+web+application+projects+from+Visual+Studio
when I upgraded to v9 from v8.2 I was getting a 500 Error on GetResource.ashx. After my upgrade I just re-deployed. I don't know what the issue was, but getting the errors, I cleared out all the files on the Azure server then deployed. This fixed my error.
Maybe one of these two items will help you.
If I read the release notes correctly, they moved the files to the UIControls library and you can still utilize the old references without issue. I've upgraded my website from 8.0.48 to 9.0.1 and 9.0.4 and had no issues. In fact, I still use the /CMSPages/GetResource.ashx?scriptfile=/path/to/file.js I believe the change was specifically to accommodate the MVC model.
We have an existing Domino 8.5.3 FP4 server that is being used for XPages application for the first time. The latest Extension Library from OpenNTF has been installed, but the issue we're having appears to be with the standard XPages runtime.
A simple XPage is displaying:
Error 500
HTTP Web Server: Command Not Handled Exception
and in the xpages_exc_XXX.log:
Caused by: org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.http.servlet
It appears to be due to WCT being reported as the version:
tell http osgi show version
XSP Runtime Version: [WCT8.5.3_FP4] 20130326.1400
What would cause WCT to be reported rather than DSI? I read it should always be DSI for Domino XPages.
tell http osgi diag org.eclipse.equinox.http.registry
Cannot find bundle org.eclipse.equinox.http.servlet.
The following files in D:\Lotus\Domino\osgi\rcp\eclipse\plugins appear to be have been updated after Domino was installed:
com.ibm.eclipse.equinox.http.registry.nl_6.2.3.20110815-1128.jar
org.eclipse.equinox.http.registry_1.0.100.v20080427-0830.jar
org.eclipse.equinox.http.servlet_1.0.100.v20080427-0830.jar
Thanks
Update 04 February 2014 09:45
I've performed the following:
tell http osgi diag org.eclipse.equinox.http.servlet
Cannot find bundle org.eclipse.equinox.http.servlet.
This does NOT list the following (which are displayed on a working server) - although bundles 0-7 and 10-152 are listed:
tell http osgi ss
8 ACTIVE org.eclipse.equinox.http.registry_1.0.100.v20080427-0830
Fragments=45
9 ACTIVE org.eclipse.equinox.http.servlet_1.0.100.v20080427-0830
Is there any further debugging I can do to determine why the bundles cannot be found?
I don't think the WCT vs. DSI label is the problem. That's just an artifact of how IBM builds fix packs. However, there does appear to be a problem with the set of OSGi plugins installed on your system.
It looks like it can't load equinox.http.registry because it can't find a required plugin -- equinox.http.servlet. Have you tried investigating why the second plugin doesn't load? In other words:
tell http osgi diag org.eclipse.equinox.http.servlet
That might help you chase down the missing constraint.