I am trying to create an instance using the Configuration Manager of WCS 7. I am working on a Win 7 x64 machine with DB2 9.5 64 bit version.
I am struck with this Massloading error when the instance creation happens :
In createInstanceANT.log file :
[Massload] Massloading
C:\IBM\WebSphere\CommerceServer\schema\xml\wcs.keys.xml Error in
MassLoading, please check logs for details.
The error log shows the following error :
[jcc][10165][10044][4.3.111] Invalid database URL syntax:
jdbc:db2://:0/WCSDEMO. ERRORCODE=-4461, SQLSTATE=42815
C:\IBM\WEBSPH~1\COMMER~2\config\DEPLOY~1\xml\createBaseSchema.xml:185:
Error in massloading
WCSDEMO is the database name. The Massloader is not able to get the URL and port to connect. It is supposedly getting them from createInstance.properties file but it is not working. The createInstance.properties file has all the details of the DB to connect.
What could be the reason for this error and how to resolve it ? Is there any configuration change that I am missing ?
Can you provide some more details.
look inside the messages.txt file located in WC_install_dir/instances/instance_name/logs
and confirm what the exact issue is. If it is related to jdbc driver being wrong I may be able to help you.
I've been running into massloading problems with external systems. Eg. databases not on the same machine as the WAS installation.
In these cases I look for the
As you can see setting the loaderDBName to just the name of the database would look on the local machine. But by changing this statement so you load with the syntax
loaderDBName=[DATABASE_SERVER_NAME]:[PORT]/[DATABASE_NAME]
You'll be able to massload using the commerce standard scripts. These changes needs to be done in many scripts. Both for updating fixpacks and enabling features. If you run database updates without the changes it will crash at first and have done all the schema changes to the database that you then need to comment out before trying again.
IBM Software Support is your friend. They'll help you fix it.
Related
From time to time when I run some queries I get this error message :
An operation that uses the database driver could not be completed. If the driver is a Microsoft driver, make sure the driver file isn't damaged
I didn't found yet how to fix it with internet help.
this last website give a "solution" but I can't do the same.
"Well in my case it worked by giving the user access to the DB it is accessing."
I just have a worksheet who use others files from my company network, I don't use any database ...
I can't reinstall the driver or anything else, my company have a very strict politic about IT security.
May I have some help ?
I had the same issue when I try to connect Analysis service in Azure. The error message is misguiding. In actual, you are missing few client drivers that are needed to connect to Azure Analysis services. Install all the missing drivers (OLEDB, AMO and ADOMD) from https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions#known-issues and you should be good to go.
I think OLEDB installation should suffice the need but I did all three to avoid future encounters related to other admin stuff. Check if OLEDB updated # C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\140 by comparing msolap.dll version. Latest version as I write this is 15.1.108.23
Tip: 1) Try connecting to Analysis Service from Excel by following the steps - Data Menu --> Get Data --> From Database --> From Analysis Services. Follow the prompts by filling appropriate info. Bingo! You are in!
2) Wait for a while if still you can't connect after installing all drivers. I don't know the actual reason why but was able to connect next day.
Please mark this as an answer if it helps to solve your problem.
Good Luck!
Update - 1/5/2021
Today I face same ugly error again which made me to rethink what else could be gone wrong in the system. Later realized that I had restarted the machine and that removed the temp connection file referred by Excel file. Following the steps to reconnect under the Tip section in above instructions let me successfully in.
I have API Connect installed with mongodb connector over a remote server.
When I access the IBM API Connect through browser, all is fine, but when I go to DataSources where my DB is, and try to hit Update Schema button as shown in the image, an error occurs showing this:
Cannot GET /apim/dataSources/partials/dataSourceMigrate.html
P.S. I gave full permission for my project directory (/var/www/) with full ownership for www-data group and still the same.
Anyhelp would be appreciated.
FINALLY AND AFTER 2 MONTHS OF WAITING, I've got an answer from IBM Bluemix Support and sorry to bring the bad news, which is the following:
Hi Ghassan,
Thanks for sending the additional files. I checked with our development team and they found a bug in the code.
The fix will be available in a future release of the apic command line, but I don't have a date for it yet.
I will further discuss the plans to release this fix and will update you as soon as possible.
IBM Bluemix Developer Support and Enablement Team
A fix has been provided for this issue in iFix versions of 5.0.3.0, 5.0.4.0 as well as newer versions of API Connect. If you are still experiencing this issue, please update to a later version that includes the fix.
For eval purpose; I installed Cognos 8.4.1 on Ubuntu 10.04.
The DB for the content store is Oracle 11g with AL32 UTF8 character set.
Crypto keys are stored locally. Env is set as recommended.
When trying to start the service, even before creating the content store, I get this message :
CM-CFG-5076 A Content Manager configuration error occurred during the initialization of Cognos Access Manager. CAM-AAA-0071 An internal error occurred. St9bad_alloc
Any idea of the cause ?
Thanks,
Fred
Using a supported distribution would definitely be a good idea. That said, if you stop cognos, rename the cogserver.log file (by default this is in /logs under your installation directory), start cognos up again and post the generated log file we might get more detail about what's stopping it.
I am trying to attach a cloud drive as described here http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Storage but I get the error ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET ?
What does this mean? I've tripled checked my config at it seems ok.
I am trying to connect the cloud drive in a Windows Service on a VM Role.
I discovered that the FixMSI.js script from http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Install was failing. For some reason $(BuiltOutputPath) was empty. I did it relative to the $(ProjectDir) instead.
It then failed with a different error (and much earlier). CloudDriveException 0x80070103.
Searching for this gave me this article which basically told me to manually edit the driver inf file for the wa miniport. http://msdn.microsoft.com/en-us/library/windowsazure/hh708321.aspx.
Now it attaches ok. The strange thing now is that the device has a warning when the vm starts (but only when hosted in azure), I have to manually go into the vm on azure and update the driver.
try to change BuiltOutputPath to BuildOutputPath. According to Richard, this is an error in the document. Refer to the Community Content section on the document for more information.
I am facing a problem while starting the websphere message engine for one of the application deployed on websphere. This application is getting deployed automatically as a part of the installation of Websphere Lombardi 7.2 express edition. It's using websphere 7 internally to deploy it. When I try to start the message engine from the administrative console of websphere I am getting following error:
The messaging engine ProcessCenter01.twperfsvr-twperfsvr_bus cannot be started as there is no runtime initialized for it yet, retry the operation once it has initialized. For the runtime to successfully initialize the hosting server must be started, have its 'SIB service' already enabled, and dynamic configuration reload enabled. If this is a newly configured messaging engine and it is the first messaging engine to be hosted on this server, then it is most likely the 'SIB service' was not previously enabled and thus the server will need to be restarted. The messaging engine runtime might not be initializing because of an error while trying to start, examine the SystemOut.log of the hosting server to check for error messages indicating the problem.
After restarting the server, the same error shows. Can anyone help me to to find what gets loaded as a part of "initialization of runtime"? Are there any config files etc. that I need to check to solve this issue? I am suspecting some missing configuration causing error to load the runtime for this particular application.
I too faced this issue today had to delete all the files under the message store
check the directory-file path mentioned in
Application servers > server1 > Messaging engines > XXX.server1-primaryBus > File store
Just Enable the SIB Services For the particular Server.
Example:Server-->Application Server-->click on Server Name-->right hand side we can see SIB services-->Check box the Enable services.
This will solve your problem
Recently I have faced the same issue when I rebuilt the jvms in UAT envt. After searching on web I found that because of the old messages saved in the message store(flat files in my envt) the messaging engines was not getting initiated. After deleting the old messaging store and restarting the servers it got initialized.
I have struggled with this problem too.
In our situation the problem was that the file message store location was used that was already created for a different (or old) message-engine.
If you add a busmember to the service-bus and use a file store implementation, then you need to supply the path for the store and log folder. Make sure these locations don't exist yet, other wise you will run in the problem above. The message-engine for this member will use these folders.
If you have a script for creating the message-bus infrastructure, make sure that when you delete the bus or remove message-engines, that you remove the file store/log folders for these, before you re-run your script.
Another possibility is that you are using a external database as a data store, and the user that is used for the connection is not allowed to create a database. You might find a ffdc entry like this:
DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=DB2ADMIN;CREATE
SCHEMA, DRIVER=3.61.65
Then you have to go to your database administration tool and give DB2ADMIN the proper privileges. Then restart the server or cluster.
Finally this issue is been resolved. I did not create the schema in SQL Server with same name as that of the username I gave to connect SQL Server during the installation of WLE 7.2
Please find details about this at below link:
http://www.ibm.com/developerworks/forums/message.jspa?messageID=14795282