I am trying to install a jar file in Sybase ASE-15.7 using the 'instjava' command.
I am getting the following error: The ASE PCI-Bridge is not able to process the requested dispatching. This is a fatal error, please contact your System Administrator (SA) for help.
I have enabled java and enabled pci using the following commands:
sp_configure "enable pci", 1
sp_configure "enable java", 1
After looking at the error on the net, i have found that the cause of the error is :
Error 16022 may be reported "The ASE PCI-Bridge is not able to process the requested dispatching. This is a fatal error, etc." when the PCI is unavailable with a stack trace in the error log showing modules "jvminit", "SYB_CreateJavaVM" and "terminate_process" although the stack trace information is unnecessary.
But there is no solution to the problem.
would anyone be able to offer any assistance in this case?
Thanks
Have you tried to restart ASE?
Also I think sp_configure "enable pci", 1 requires that the sybpcidb database be created if it does not already exist.
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
Running IIS 7.5 on Win2008. Trying to change the App Pool Identity to Administrator user. When I click OK on the dialog, I get this error: "Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
I have tried IISRest and also Restart the sever But issue didn't fix.
Below is the error from Event Viewer
An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by EDC2010-TEST\SPDatabaseConfig, in the OWSTIMER (1172) process, on machine EDC2010-TEST. View the tracing log for more information about the conflict.
Try to re-install IIS by using the server manager. According to Microsoft, this is a machine key corruption issue, which is used to encrypt and decrypt application pool identity credentials.
https://forums.iis.net/t/1180041.aspx
This is a Microsoft system-level problem, namely running out of interrupt request stack space, which can be fixed by making a registry change to allocate a larger IRPStackSize. It is discussed in the below link.
https://support.microsoft.com/en-us/help/106167/error-message-not-enough-server-storage-is-available-to-process-this-c
https://appuals.com/fix-not-enough-storage-available-process-command/
Feel free to let me know if there is anything I can help with.
This has solved the problem for me.
So I had a similar error and I could not find a resolve in any forums.
I'm using the "WMI Provider Host" to edit bindings in IIS using VBScript.
Anyways after trying a few suggestions such as netsh http delete sslcert ipport=0.0.0.0:443 Here and editing the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters > IRPStackSize Here.
I noticed when running my application the "WMI Provider Host" was getting to ±512MB in the ram and found that C:\Windows\System32\inetsrv\config\applicationHost.config was well over that size.
That's when I found this link to increase the memory allocation to the service.
Hopefully it helps.
I have inherited support of a product which after 2.5 years without issues is now throwing the following exception:
"ThoughtWorks.CruiseControl.Core.CruiseControlException: Error creating VM [Unable to create VM based on [Template_VS2013]. Error: The specified key, name, or identifier 'Template_VS2013' already exists.]"
I have no direct access to the production environment but it appears that there the key and name do not actually already exist. I inherited some support documentation which states that this error is caused by lack of space on the server the code is running on but there are TBs of free disk space.
The code is C# using CruiseControl.Net
Does anyone have any insight as to what could be causing this?
Thanks
It seems that this is caused by a VMWare bug with caching: https://communities.vmware.com/thread/476449
We are working on a workaround / fix at the moment
I am really stuck in ClearCase startview on Linux. I tried the below:
ct startview <viewtag>
And met an issue like below:
cleartool: Error: Unable to create directory "": error detected by ClearCase subsystem.
I am sure the view is OK, and I can start it in other host. So perhaps my OS met some issue. Is there some good solution?
And I have restarted my Linux system.
If this is about a dynamic view, you can check technote swg21449500 "Create and startview errors: Cannot start dynamic view and Unable to create directory":
Cause
The client or view-server installation is corrupted. The symptoms would typically be seen immediately after applying a Fix Pack of iFix.
Diagnosing the problem
A cleartool -verall showing a mismatch between the MVFS and the other modules is a clear indication of corruption.
Resolving the problem
An uninstall and re-install on the machine will be necessary to resolve the issue.
On Windows, you can see a similar error when a Windows client attempts to start a dynamic view on a Linux or UNIX server running Samba.
See swg21295394.
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.