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.
Related
I have a web .net application, it will read an excel file using the Microsoft Access Database Engine. It works fine , but recently it is giving some error. From the log, these 2 points i think are the highlight, which I still could not find a solution. I have tried reinstalling Microsoft Access Database Engine, but not helping. Google for it, but didn't manage to get a hint as well.
One funny thing is whenever it happened, I recycle the app pool on IIS and issue was resolved. But then the issue will come back very quickly. If anyone had come across this, would appreciate any help. Thanks.
The .Net Framework Data Providers require Microsoft Data Access Components(MDAC). Please install Microsoft Data Access Components(MDAC) version 2.6 or later
Retrieving the COM class factory for component with CLSID {2206CDB2-19C1-11D1-89E0-00C04FD7A829} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA)
To resolve this problem, please follow official doc to try.
Method 1
Do not log on to the server for interactive sessions by using a service account.
Method 2
Disable the related Windows User Profile Service feature.
For more details, please read this article.
"800703fa Illegal operation attempted on a registry key" error
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.
Been facing this for a few days already. I wonder if there's anyone else having this kind of issue.
I go to My Apps in JIRA and select "Azure Pipelines for JIRA" then click on "Get Started" (I had already configured this once so it worked before) and get the following error:
Error and console from JIRA
It mentions deprecated JS, cookies, and a server 500 error. Not sure what needs to be done here.
I can reproduce this issue and try to install the plugin via a new account again, I will get the 500 issue.
I have report this issue in the GitHub and Azure DevOps Developer Community, you could follow these links to get the latest news.
Thank you for helping us build a better Azure DevOps.
Update1
Produce team response:
We have run into additional issues, and would need a couple more weeks. I am working on it to get the fix in place as soon as possible.
After upgrading system to Windows 10 - os 1803 we are getting below issues while working with ClearCase 8.0.1.x/9.0.1.x
Unable to checkin/checkout.
Not able to create views.
Not able to add any file to source control.
The system hangs & crashes while performing any ClearCase operation.
There is no error message, but I have attached screenshot for reference.
Please let us know if there is any issue with the Windows 10 ver(1803), any security system enabled?
Or has ClearCase provided any fix?
We have tried 9.0.1.5 and issue still persists.
This is what we got from windows event log.
The computer has rebooted from a bugcheck.
The bugcheck was:
0x000000c2 (0x0000000000000004, 0x00000000535be990, 0x000000000004efd3, 0xfffff803e01848b1)
for most of them whoever has upgraded to windows 1803 ver :( for people who are still using ver1709 it is working perfectly fine
Then I would recommand contacting IBM support: only them can update their ClearCase 9/Windows 10 compatibility matrix and confirm if MVFS is supported on a more recent (1803) Windows 10 edition.
We also facing same problem and I have raised the case with IBM. Still not yet resolved. As IBM said there are some limitations to work ClearCase with windows 10 and windows 2016.
We tried all the options except Secure boot disable. If possible please do disable secure boot option in Windows 10 and try to checkin/checkout code from CleraCase
Note : It works for Snapshot views. That means the issue related to MVFS
I'm seconding #VonC's recommendation to open a ticket with IBM. When you do that, save a step and collect a clearbug2 and a kernel memory dump to send in as soon as the case is opened. It will save the turn-around time of us asking you for it. If the installed programs list doesn't list installed security software (DLP, Privilege management sw like Avecto, other endpoint security tools), please list those separately as well.
I would also love to know who # IBM told you there are "limitations" with Win10-1803.
There are a few issues with Windows 10 "version upgrades" breaking things, but they generally don't cause system crashes. Windows 10 upgrades are actually full OS installs that then (imperfectly) migrate application settings. Anything that uses custom network providers (ClearCase is one example) will find that the network providers will be broken or partially broken. Reinstalling is usually required. Again, that has not yet been reported as a cause of a BSOD.
If the upgrade/reinstall didn't fix view creation, please post a separate question on the view creation issue. There may be things we can do to the SMB 2 caches to allow view creation to work in cases where the view storage is not on the client host.
I noticed that the screen shot you posted is a Terminal Services disconnect screenshot. Does the issue only occur over a Terminal Services client connection or does it also happen on a local connection?
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.