Hybris: 6.3.0.25
When initializing Hybris 6.3.0.25 with platformbackoffice extension, the initialization never finishes.
Is there a workaround to fixing this issue?
STEPS TO REPLICATE:
Download and Extract ZIP file of Hybris 6.3.0.25
In platform folder, do ant all using default settings
In localextensions.xml, make sure platformbackoffice is the only extension
In platform folder, do ant initialize
Start Hybris
Open HAC and do Platform Intialize
NOTES:
Nothing is added in local.properties. So, Platform Initialize will use in-memory DB. However, the same issue also happens with mySQL 5.6.42.
Issue also happens with Hybris 6.3.0.24
The issue does not happen in Hybris 6.3.0.0-SNAPSHOT
I am planning to upgrade from Hybris 6.3.0.0-SNAPSHOT to the latest 6.3, which would be 6.3.0.25 at the time of this writing. Before that, I also tested with 6.3.0.24 and the upgrade didn't go so well.
ACTUAL RESULT:
Hybris hangs.
EXPECTED RESULT:
Platform Initialize finishes successfully
LOGS:
https://pastebin.com/Sx0223UM
I don't think so, only platformbackoffice can be running. You need more modules then it. I haven't got exact list, you can check dependencies in module config xml file (extensioninfo.xml). It is giving error about missing cockpit config with below message in your log file.
[DefaultCockpitConfigurationService] Could not load cockpit configuration root element; creating new one
What is your aim for running only platformbackoffice?
Related
I'm trying to implement custom dotnet host in C++ by using hostfxr:
https://learn.microsoft.com/en-us/dotnet/core/tutorials/netcore-hosting
It works, however System.AppDomain.CurrentDomain is not initialized correctly.
For example, AppDomain.CurrentDomain.BaseDirectory is empty.
Is it possible to configure the default AppDomain by using only nethost.h and hostfxr.h headers or should I rather go deeper and try to touch coreclr.dll API?
I found it.
The following coreclr runtime property must be set:
hostfxr_set_runtime_property_value(ctx, L"APP_CONTEXT_BASE_DIRECTORY", L"path\\to\\application");
This way AppDomain.CurrentDomain.BaseDirectory is getting initialized.
.NET 3.1 App was working fine before but today after I tried to run it through IIS, it is giving me this error.
given messsage error
browser shuts down after this
This is how event viewer looks
and also I noticed something, I'm not sure if it is important, in applicationhost.config there are lines about .Core2 (I'm using .Core 3.1)
I solved it by creating a new project and copying everything (except Program.cs and Startup) in it with some necessary configurations in Startup.cs like ConnectionString and Mapping
You could have also enabled the startup errors logging.
That way you would know what went wrong for the next time.
I'm fairly new to Flex\AS3
I'm using flash builder 4.5 for php and I'm trying to connect to my DB via remote objects.
I'm following adobes instructions as listed here:
http://help.adobe.com/en_US/flex/accessingdata/WSbde04e3d3e6474c4-668f02f4120d422cf08-7ffe.html#WSbde04e3d3e6474c4-668f02f4120d422cf08-7ffa
I've created the php service, and successfully finished the wizard.
I've tested my service with the Test tool and it is indeed returning my results.
My problem is that it seems that flash builder didn't create the service's files(super+base) at all. For example, when I drag the service into a dropdown component I get an error saying that the service component can't be found.
Does anyone know this issue happens? how can the test tool work if the service classes don't exist?
Thanks in advance,
Ravid
The problem was that I didn't checkout the files before using the wizard so flash builder didn't have write permissions on the files and therefore didn't create the necessary files.
once he had the write permissions - everything worked just fine
I recently take over a web application project using websphere and log4j running under AIX. To create a development environment, I setup all the components in windows, using eclipse to compile a WAR file and deploy it.
All is working fine except that log file is not created.
I changed the log file in log4j.properties from something like in below and and give everyone full access permission to the directory:
log4j.appender.F1.File=/abc/def/logs/admin.log
to
log4j.appender.F1.File=c:/logs/admin.log
What else can I check?
I create a simple standalone testapp which use the same log4j.properties and it can create the log file, but when the servlet deployed to websphere, it doesn't work. Please help! Thanks!
Ok, I think this article should help you. It seems that WebSphere CE uses log4j by default and controls it with a global properties file. There is a section on how to use application-specific properties files.
Here is what I try and do to troubleshoot similar issues.
Turn on log4j debugging to see where it actually picks up the file from. You need evidence of which file is picked up (so turning the debug on is a worthwhile activity) This provides you information with what log4j is trying to do to locate the configuration file.
-Dlog4j.debug=true
I would not hardcode the log4j location in the code. Instead I
would use the log4j.configuration System property and state that in
the JVM arguments. This way even I don't need to touch my code.
-Dlog4j.configuration=file:///home/manglu/log4j.properties
I would use this approach irrespective of the runtime server that I use (be it Tomcat or WAS CE or WAS)
Hope this helps
I suggest you use environment variables set on your server like this :
You must access the admin console of your server.
Under custom properties
Server_path=/abc/def/logs
In your log4j, use this : {$server_path}/log.txt
Make sure the user running the app has access to that directory.
I am using a COM dll in my .Net web application. This works fine on multiple different machines.
However on one particular machine I get the following error:
Unable to cast COM object of type 'CServer.CApplicationClass' to interface type 'CServer.ICApplication'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CF0DFA28-046B-4C7D-8AA9-F4B7477D8CAE} ' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
I have registerd the dll using the regsvr32 command.
I have also created a COM+ application for this dll.
Running a search through the registry
I can find the key in numerous places.
I have also tried unregistering the dll and deleting all referneces on the computer to this dll. And afterwards re-adding the dll and re-registering it.
I have written a simple windows script file which tests the dll. This works fine. However the problem exists in my .net project which is running in iis.
Can anyone help me with this?..
If you need anymore info please leave a comment. Thanks.
I had a similar problem, with the "TYPE_E_CANTLOADLIBRARY" message.
Background:
I had a project which used Interop.ReferenceA.dll. This file was created using tlbimp ReferenceA.dll /out: Interop.ReferenceA.dll.
Solution:
When I took a look at ReferenceA.dll using RegDllView I noticed that ReferenceA.dll had a subclass, which was the IID shown in the error message.
I looked around in the source code of the subclass and noticed that it had a dependency to Interop.ReferenceB.dll.
Turns out that the subclass needed Interop.ReferenceB as a type-library to work. So I ran this:
regasm /tlb:Interop.ReferenceB.tlb Interop.ReferenceB.dll (the 32-bit version of regasm was used.)
And the error went away.
Make sure your AppPool is set to x86. Also make sure your assembly is targeting only x86.
I was having a similar issue. First got Access Denied, which after some looking around was resolved, only to be faced with this error message (TYPE_E_CANTLOADLIBRARY). Mind that I'm running a COM+ Component on Windows 7.
After some fruitless attempts which involved messing with the registry, my workmate and I found a way of getting it up and running:
1) Unregister your dll (regsvr32 -u dllname)
2) make sure your references to the dll are cleared up from registry (backup first)
3) Create an empty com+ application (server app) in Component Services
4) Copy the application id to the clipboard
5) go to "c:\program files (x86)\Complus applications" and create a folder with the id on your clipboard
6) copy your dll into that folder and register it
7) Go back to your Component Services and add the component to the app you created using the dll on "c:\program files (x86)\Complus applications{*app id*}"
that did it for me. Hope it helps.
I had a similar problem where the error was triggered on my PC but not on that of other developers.
It turns out that I had been testing an automatic build process on my PC that had updated the version number of the assembly, thus registering the TLB in the registry with a version number higher than the one we were normally using.
When trying to get the interface, the server was consistently using the wrong TLB information leading to the wrong assembly. Once I deleted the higher version entry in the registry, it worked fine.
Now we just have to ensure the build process is not going to cause that issue again. :)