Oracle Application Server 10g
Operating System: Unix
I got the below error:
frm-92101 there was a failure in the forms server during startup
The solution in windows as follow:
control panel ( Middle tier) , click on the OPMN for middle tier -> LOG ON ->
Check Allow Service to Interact with Desktop
How can I apply the above solution in UNIX?
missing rpm openmotif21-2.1.30-11.EL5.i386.rpm on Linux OS.
Project downloads
Related
I received the message "WebSphere application server v7 is currently running. Please shut it down to continue." while attempting to upgrade my local version of WebSphere Application Server 7 using IBM Installation Manager on Windows 7. The server was not running at the time. The message also persisted after a reboot.
According to this technote, any running Java process can cause this issue. I found a running instance of javaw.exe using Process Manager, closed it, and the installation was able to proceed from there.
I feel that the title pretty much speaks for itself. I keep getting a server 500 error when i try to access a page on my site that is using the Access DB.
I created an ODBC (32 bit) Data Source using the driver Driver do Microsoft Access (*.mdb).
I am sure i am using the wrong drivers/IIS configurations. This used to be hosted on an old server and we are trying to move everything over.
Would anyone be able to point me in the right direction? Thanks!
EDIT
I was able to get errors printed to my page. Below is the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found
and no default driver specified
When I enable 32-bit Applications I get the following error:
HTTP Error 404.17 - Not Found
The requested content appears to be script and will
not be served by the static file handler.
This issue is related to running 32bit applications on a 64bit server. Furthermore, if you have installed something else on it (for example, Outlook Web Access, or OWA for short) it can disrupt the IIS with adding it's 64bit modules to load globally, and that would effectively cause errors on 32bit pools.
The following debugging is assuming you have a requirement to run 32bit ASP application on a 64bit IIS server.
You have to set your application pool to run as 32bit
If the 32bit pool stops right after you make a request for an ASP page, it means that most probably there are 64bit modules failing to load. You need to see which dll is creating the issues by viewing the Windows Event log (eventvwr). Then, one by one, you edit the applicationHost.config file and add preCondition="bitness64" to each module that you see in the eventvwr until you get rid of all the errors in the log.
When finished with step #2, your pool should be working, but your app might not - it will most probably report 404.17, even if there is an ISAPI handler for ASP. When you open IIS, on the left side choose the server and on the right open the ISAPI and CGI restrictions. You will see that there's an ASP entry there (if not - you need to install it as a feature on the server). The ASP might point to something like %windir%\system32\asp.dll, but you need to make another entry. Your appPool is running as 32bit on a 64bit machine (that's shortened as WOW64 = 32bit Windows application running on Windows 64bit - Windows on Windows64), and you need to add an asp from %windir%\SYSWOW64\asp.dll. Also, add the corresponding handler (navigate to handlers, and practically repeat the entry for asp but use the SYSWOW64 folder instead of system32)
This should (finally) get it working.
I am trying to install SQL Server 2008 Enterprise Edition on Windows Server 2008. I have done all the process till the Installation correctly. However, the installer displays the message "Managed SQL Server Installer has stopped working".
No online Solution has been provided yet....
Anyone sorted this problem before?
This is usually a problem with your installation of .NET framework. E.g:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/34671131-a095-4068-b4d8-ab5ef6f5b8cc/managed-sql-server-installer-has-stopped-working
Check that your installations are all in working order by using the tools on this site:
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
You may have to re-install any or all of your .NET framework versions.
Instead of trying several methods that have not been approved, it is better to repair the MSSQL Server installation. On the other hand, there is some other issues that can be encountered during the repair process i.e. Installing the .NET Framework 3.5 on Windows 8, Windows 8.1 and Windows 10 as shown below.
In this case, if you have trouble during .NET Framework installation, you can install it by following the steps below (requires Windows 8, 8.1 or 10) setup disc or ISO file):
1) First you'll need to copy Windows 8 setup files to your hard disk. If you have Windows 8 setup ISO copied in your system, you can mount it by right-click on it and select "Mount" option or you can extract its content using 7-Zip.
If you have Windows 8 setup disc and don't want to copy its content, its ok. Just insert the disc in your CD/DVD drive so that Windows can access its content.
2) Now open Command Prompt as Administrator as mentioned here and then provide following command:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:F:\sources\sxs /LimitAccess
Here "F:" represents the CD/DVD drive letter in your system which contains Windows 8 setup disc. Replace it with the correct drive letter according to your system.
If you extracted Windows 8 setup files in a directory, replace F:\sources\sxs with the correct path.
3) As soon as you execute the above mentioned command, Windows will start installing .NET Framework 3.5 in your system and it'll not require Internet connection.
It'll take a few minutes and you'll get a message that the operation completed successfully.
4) That's it. Now you have installed .NET Framework 3.5 in Windows 8 without using Internet connection.
For more information have a look at How to Install Microsoft .NET Framework 3.5 Offline in Windows 8 and Later without Internet Connection?. Hope this helps...
I have Oracle 64-bit client installed to run with my weblogic application. I learnt that pl-sql developer doesn't work with oracle 64-bit client so now i have both 32-bit and 64-bit clients installed on my machine and my ORACLE_HOME variable points to 64-bit client.
I am not able to start pl/sql developer even i specify the 32-bit client in Tools->Preferences of pl-sql developer version 8.0.4.
I changed my oracle client to 32-bit client then i was able to start pl-sql developer but my application doesn't work.
Is there a way i can run PL/SQL developer whilst pointing ORACLE_HOME to 64-bit oracle client. I am not sure specifying the ORACLE_HOME explicitly in Tools->Preferences of pl sql developer (for user/default as well as system preferences) has any effect as it picks the oracle home from the environment variable i believe.
Thanks,
Adithya.
You'll need to install the two clients into separate Oracle Home locations, for example I've gone for C:\OracleHome and C:\OracleHome32
Then set up an Environment Variable, called TNS_ADMIN with the folder that contains your default TNSnames.ora file as the value (for me it is C:\OracleHome\network\admin)
Keep your preferences in PL/SQL Developer, and make sure you also specify the OCI library (mine is C:\OracleHome32\oci.dll)
Finally, using regedit.exe, add a second key under ORACLE (HKEY_LOCAL_MACHHINE\SOFTWARE\ORACLE). I've called mine KEY_OraClient11g_home1 and KEY_OraClient11g_home2. Create the same 4 strings in the second key, with the appropriate changes to the data (e.g. ORACLE_HOME should have C:\OracleHome32 as it's data field in my example)
Restarting all applications should now let you use PL/SQL Developer seamlessly, whilst also defaulting to the 64-bit Oracle home for your weblogic application.
To fix this, download the 32-bit version of Oracle Instant Client, extract it to a directory such as C:\instantclient.
Next, configure PL/SQL Developer to use this version by clicking on Tools -> Preferences. Under Connection -> Oracle Home, point to the location where you had extracted Instant Client (C:\instantclient), and under Connection -> OCI library, point to the oci.dll file in the same directory (C:\instantclient\oci.dll).
Restart PL/SQL Developer and you should be able to connect.
This is an updated answer specifically for the Oracle 19 instant client and PLSQL Developer 13, which is 64 bit.
To make PL/SQL Dev work with the client, I went to :
Configure -> Preferences -> Oracle\connection -> set oracle home to the new home dir, in my case, c:\oracle\product\19.x.
Do the same for the OCI : C:\oracle\product\19.x\instantclient_19_6\oci.dll
If you're migrating from an order version, you probably have built up a list of databases in your tns_names.ora. That will have to be moved over to the new client directory tree.
Manually make a subdir network\admin under the 19.x root. Once restarted, the Database list under 'Define Connection' had my list.
Quick post: I was trying to connect to a 64-bit Oracle database using PL/SQL Developer. Despite ORACLE_HOME being set the right values and oci.dll available, PL/SQL Developer could not connect to the database.
Further probing indicated that the Oracle installation was a 64-bit one, and PL/SQL Developer is incapable of loading 64-bit version of oci.dll file. To fix this, download the 32-bit version of Oracle Instant Client, extract it to a directory such as \instant_client.
Next, configure PL/SQL Developer to use this version by clicking on Tool menus -> Preferences. Under Oracle Home, point to the location where you had extracted Instant client (\instant_client, in this case) and under location of OCI Library, point to the oci.dll file present in location where you had extracted Instant client ( \instant_client\oci.dll). Restart PL/SQL Developer and you should be able to connect now.
open given link to download oci.dll file
http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html
I have a running sql server installation on which I would like to install the reporting services module. Now because it is very important that the sql server it self keeps available and running without any interruptions I get a little scary about this step.
Now my question. Are there any pittfalls I have to be aware of before I install the module? E.g. does the server restart during the installation?
Can you try this change in a virtual machine first?
For example, use the Disk2vhd application (http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx) to make a snapshot of your current production system. Then, use the VHD that was created in Microsoft Virtual PC, Hyper-V, or Windows 7 native VHD boot.
If you try a virtual machine for testing, disable networking or create a private network before starting the virtual machine! Having two servers with the same name and SID on your network is a Bad Thing.
(If you're not using virtual machines, isn't it time? :)