OIM server running but error 404

hello experts,
I have started OIM server and its in running state in both cmd and weblogic(7001, server status) but while opening it in web console am getting error 404 page not found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Kindly suggest.
Regards,
Karan

hi
Current staus in deployements tab of oim_server
DMS Application (11.1.1.1.0)     Active     Web Application     5
Nexaweb     Active     Enterprise Application     45
oim (11.1.1.3.0) Failed     Enterprise Application     47
OIMMetadata (11.1.1.3.0)     Failed     Enterprise Application     46
RoleSOD     Active     Enterprise Application     50
spml-xsd     Active     Enterprise Application     49
wsil-wls     Active     Enterprise Application     5
wsm-pm     Failed     Enterprise Application     5
FYI : yesterday I have worked on web console, and it was working fine.
Regards,
Karan

Similar Messages

  • OIM server running but webconsole and design console not opening

    Hi All,
    I configured OIM in my machine by giving the following OIM HTTP url during installtion : http:/xxx.xxx.x.7:14000.
    The configuration was successful and i was able to work in both design and web console(http://localhost:14000/oim) of OIM for many months.
    But all off a sudden, the OIM consoles are not opening though the OIM server is in running mode (Verified thro Weblogic web console). And i also found that my my local ip address changed to xxx.xxx.x.6.
    I doubt that this behavior is due to the change in my system ip address.
    Am i right or could there be any other reasons? if yes, Is there anything i can do now?
    Any help is highly appreciated.
    Thanks
    Pria

    No, both the ways did not work for me.
    I updated my host file as below and tried accessing the webconsole(http://old ip:14000/oim) but it did not turn up.
    new ip address    http://old ip:14000/oim
    I hope the above is correct.

  • The remote server returned an error: (404) Not Found.

    Hi All
    Now I try to deploy my SAP Portal Project it gives following error message "The remote server returned an error: (404) Not Found.". What is missing?
    Regards

    Hi,
    In order to check if those seetings are ok, do following:
    Open internet explorer (or another) browser and go to
    http://localhost:50000/irj
    You should get the Portal homepage with login screen.
    If you don't - then you have a problem with your local portal ( may be it is not running ).
    If you do - Login with username: administrator and
    password: abcd1234
    If you don't succeed to login, then you have a problem with your user( may be it does not exist ).
    Regards,
    Rima.

  • The Remote server returned an error (404) not found in SharePoint Client Context code

    Hi All,
    I am getting an error with below line.
    "The Remote server returned an error (404) not found"
    It occurs when I am trying to fetch some data from SharePoint 2010 List.
    For eg. I have a webpart in which i am showing some content on page load and that content is coming from a List.
    But I am getting error.
    Screen shot for your reference.

     Here is my code:
       ClientContext context1 = new ClientContext("site url");
                context1.AuthenticationMode = ClientAuthenticationMode.Anonymous;
                List list1 = context1.Web.Lists.GetByTitle("List1");
                CamlQuery query1 = new CamlQuery();
                query1.ViewXml = @"<Query><Query><OrderBy><FieldRef Name='Title' Ascending='True' /></OrderBy>      
       </Query></Query>";
                Microsoft.SharePoint.Client.ListItemCollection listCollection1 = list1.GetItems(query1);
                context1.Load(listCollection1);
                context1.ExecuteQuery();  
               Even i removed the line no. 2 from above code and placed below but still same issue.
               context1.Credentials = new NetworkCredential("user", "password", "domain");
    Hope someone will solve my issue here.

  • Managed server now working: Error 404--Not Found

    Hi All,
    I am very new to this field and have just installed weblogic server 10.3.3.
    I have created an Admin server and a cluster of two Managed servers.
    Admin server is working and is opening in the UI console.
    When i am starting the Managed server, in the cmd console it is showing
    <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    but in UI it is showing as :
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    how to start Managed Weblogic server?
    TIA,
    Vishal

    Hi Sandeep,
    yes i m using http://host-name-of-Admin-Server:Port/console to check the status.
    i have clustered the two managed server.
    To start the Managed server i m using the command:
    startManagedWebLogic.cmd ms_1 http://localhost:7001
    and in the cmd console i am getting message as:
    <Mar 17, 2011 4:23:03 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Mar 17, 2011 4:23:04 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 17, 2011 4:23:04 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing se
    lf-tuning thread pool>
    <Mar 17, 2011 4:23:04 PM IST> <Notice> <LoggingService> <BEA-320400> <The log fi
    le C:\Admin\Middleware\user_projects\domains\base_domain\servers\ms_2\logs\ms_2.
    log will be rotated. Reopen the log file if tailing has stopped. This can happen
    on some platforms like Windows.>
    <Mar 17, 2011 4:23:04 PM IST> <Notice> <LoggingService> <BEA-320401> <The log fi
    le has been rotated to C:\Admin\Middleware\user_projects\domains\base_domain\ser
    vers\ms_2\logs\ms_2.log00001. Log messages will continue to be logged in C:\Admi
    n\Middleware\user_projects\domains\base_domain\servers\ms_2\logs\ms_2.log.>
    <Mar 17, 2011 4:23:04 PM IST> <Notice> <Log Management> <BEA-170019> <The server
    log file C:\Admin\Middleware\user_projects\domains\base_domain\servers\ms_2\log
    s\ms_2.log is opened. All server side log events will be written to this file.>
    <Mar 17, 2011 4:23:06 PM IST> <Notice> <Security> <BEA-090082> <Security initial
    izing using security realm myrealm.>
    <Mar 17, 2011 4:23:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STANDBY>
    <Mar 17, 2011 4:23:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to STARTING>
    <Mar 17, 2011 4:23:09 PM IST> <Notice> <Log Management> <BEA-170027> <The Server
    has established connection with the Domain level Diagnostic Service successfull
    y.>
    <Mar 17, 2011 4:23:09 PM IST> <Notice> <Cluster> <BEA-000138> <Listening for ann
    ouncements from cluster Cluster_1 on 239.192.0.0:8050.>
    <Mar 17, 2011 4:23:09 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchr
    onize with other running members of Cluster_1.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Cluster> <BEA-000142> <Trying to downloa
    d cluster JNDI tree from server ms_1.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Cluster> <BEA-000164> <Synchronized clus
    ter JNDI tree from server ms_1.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to ADMIN>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to RESUMING>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async"
    replication service with remote cluster address "127.0.0.1">
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090171> <Loading the iden
    tity certificate and private key stored under the alias DemoIdentity from the jk
    s keystore file C:\Admin\Middleware\wlserver_10.3\server\lib\DemoIdentity.jks.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted
    certificates from the jks keystore file C:\Admin\Middleware\wlserver_10.3\server
    \lib\DemoTrust.jks.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted
    certificates from the jks keystore file C:\Admin\Middleware\jdk160_18\jre\lib\se
    curity\cacerts.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
    loading of the trusted certificate list raised a certificate parsing exception
    PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
    \,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
    arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
    0.113549.1.1.11.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
    of the trusted certificate list raised a certificate parsing exception PKIX: Un
    supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default"
    is now listening on 10.174.4.84:7201 for protocols iiop, t3, CLUSTER-BROADCAST,
    ldap, snmp, http.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSe
    cure" is now listening on 10.174.4.84:7202 for protocols iiops, t3s, CLUSTER-BRO
    ADCAST-SECURE, ldaps, https.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1
    ]" is now listening on 127.0.0.1:7201 for protocols iiop, t3, CLUSTER-BROADCAST,
    ldap, snmp, http.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSe
    cure[1]" is now listening on 127.0.0.1:7202 for protocols iiops, t3s, CLUSTER-BR
    OADCAST-SECURE, ldaps, https.>
    <Mar 17, 2011 4:23:24 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started We
    bLogic Managed Server "ms_2" for domain "base_domain" running in Development Mod
    e>
    <Mar 17, 2011 4:23:26 PM IST> <Notice> <Cluster> <BEA-000102> <Joining cluster C
    luster_1 on 239.192.0.0:8050>
    <Mar 17, 2011 4:23:26 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to RUNNING>
    <Mar 17, 2011 4:23:26 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
    rted in RUNNING mode>

  • Can't login to EM & ODSM when OIM server running..

    Hi Oracle specialists,
    I have a strange problem and I hope you can help me out with this... I'm almost finished installing Fusion applications and have the following servers configured for IDM:
    -Admin Server (console/EM)
    -wls_oam1 (OAM)
    -wls_ods1 (ODSM)
    -wls_oim1 (OIM)
    -wls_soa1 (SOA)
    The thing is that as soon I start OIM, I can't login to ODSM, the login page becomes unreachable. I also can't login to EM since the SSO login credentials (weblogic_idm) are not accepted. BUT I can login to OIM with weblogic_idm.
    But when I shut OIM down and restart the other servers, I have perfect SSO functionality with user weblogic_idm. The strange thing is that it used to work and I'm trying to avoid reinstalling Fusion Applications all over again.
    I hope you can help me out!
    Greetings,
    Charif

    I also get this error message when trying to access weblogic administration console while OIM is running:
    Failure of server APACHE bridge:
    No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

  • MySQL SERVER NOT FOUND ERROR 404

    Having talked to as many people as should know, NOBODY seems
    to have a clear answer to the fact that from Dreamweaver 8 there is
    a serious connectivity issue to MySQL databases in PHP server. I'm
    using Easy PHP.
    I begin to wonder if the makers of Dreamweaver8 intended to
    give us all a Jigsaw puzzle. This Problem Error 404 not being able
    to find the PHP@MySQL server/database is getting increasingly
    ridiculous that I might begin to suggest that people never buy
    Dreamweaver8 as it is more trouble than any good. How can Adobe sit
    bag and let us keep going through this stress?
    How does one determine a more uptodate library when you have
    just installed the latest version of Dreamweaver 8 and
    EasyPHPserver? You still keep getting the error message that it
    cannot find MMHTTPDB which is sitting clearly in the appropriate
    folders!!
    In the previous versions, it was straight forward on IIS to
    set up a DSN and just connect to the Database. Why has it become
    impossible to connect to a straightforward and existent database?
    I am disappointed with Adobe amd Dreamweaver makers! I've
    over stressed myself trying to get this problem solved.
    Help Pleeeease!!!

    IfyO wrote:
    > Having talked to as many people as should know, NOBODY
    seems to have a clear
    > answer to the fact that from Dreamweaver 8 there is a
    serious connectivity
    > issue to MySQL databases in PHP server.
    There is not a serious connectivity issue. It works perfectly
    on
    correctly configured system. I have given you a full response
    in your
    duplicate post in the "Can't connect to MySQL" thread.
    David Powers
    Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
    Author, "Foundation PHP 5 for Flash" (friends of ED)
    http://foundationphp.com/

  • ICal Server running but not Running

    I'm trying to get iCal server working. It looks as if it is running from within ServerAdmin but when I try to log in to iCal from Safari I keep getting the error Unable to Access calendar, because the calendar server is not running. Any help would be great.
    Brad

    Our Ical server have stop working after 10.5.8 update.
    Show these log:
    Jun 8 21:35:30 xserve01 com.apple.launchd[1] (org.calendarserver.calendarserver): Throttling respawn: Will start in 10 seconds

  • Dispatcher ,SDM, Server running But shows NULLPOINTER

    HI All,
    I have a strange problem , dispatcher,sdm and server are running fine.I can access useradmin,sld,index.html easily but when i try to access /irj it is throwing an error.(NULL POINTER EXCEPTION)
    Can anyone help me in this regard.
    In case some one wants log file details please let me know the location of the same.
    Thanks
    Pankaj

    first I would look at the server process trace (server0 etc), if no error detected you have to try
    SAP NetWeaver Application Server

  • Nimatlabserver indicates server running but port not open

    I have a problem, where matlab release13 tells me that the server is running on xxx port when loaded but checking that with netstat -na from a command prompt the xxx port is not open. My main issue is that I can't figure out why the server doesn't open the port? Anyhting you might have learned would be helpful. I used the main.vi to call the SIT start server.vi and I can see then that the port 6011 is open. I tried multiple ports to open in matlab but nothing works. I am using SIT v2.0

    Timmy,
    If the SIT server is able to open port successfully, netstat -na will show a TCP port 6011 in Listening state. Failure to open the port should cause an error dialog and is most commonly caused by another application already using the port. More information is needed to diagnose the problem, but make sure that no windows security feature is interfering (ex. windows XP SP2 network security setting)
    It is not possible to start multiple ports in one matlab process. You will need to start multiple matlab processes and start server by typing 'NiMatlabServer('start',6012)' for example.
    -SumitG

  • OBIEE 11g Server running but URL dashboard not opening

    Hi My admin and BI manage server is running however i am not able to open the Dashboard. it is giving me the below URL...
    Error 500--Internal Server Error
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    *10.5.1 500 Internal Server Error*
    The server encountered an unexpected condition which prevented it from fulfilling the request
    Also do any of you have any idea what is the password of SampleAppLite.rpd
    and what is the maning of two passwords when we open any RPD in online mode?

    Hi,
    I had the exact same problem.
    To solve the problem, I made sure that the RPD password was correct. I had typed this incorrectly (probably with Caps Lock on) when putting in the SampleApp RPD.
    You can modify this password by going to the FM Enterprise Manager:
    http://<server>:7001/em/
    - After logging on, go to Farm_bifoundation_domain / Business Intelligence in the tree on the left
    - Select coreapplication
    - On the right, select the "Deployment" tab, and the "Repository" subtab
    - Click Lock & Edit Configuration button
    - Change the repository password, make sure it is correct - I did this by typing the password in a notepad file, and to check it I opened the RPD file in offline mode in the administration tool, and then copy/pasted the password in. If the RPD file opens without problems in the AdminTool, then copy/paste the password into the two fields in the Enterprise Manager.
    - Click Apply and then the Activate Changes button
    - Now you need to restart the services. Click the link "Restart to apply recent changes". This will take you to the "coreapplication" - Overview tab, where you can click on the blue "Restart" button to restart the services.
    After restarting it worked fine for me.
    Hope this helps!
    Best regards,
    Henrik Norhøj Nielsen

  • Error 404 -- Not Found, when a Servlet is invoked from browser

    Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
              even the simplest servlet.
              I painstakenly went through all the steps that are listed in the WebLogic
              Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
              have missed a step somewhere.
              I have modified the weblogic.properties file as per all the instrustions,
              but the server simply won't recognize any servlets, not even the SqlServlet
              that came with the server as an example.
              It would require more than 1 exchange of posts to resolve it for me, and I
              am wondering if one of you is willing to work with me on this until I have
              managed to configure the server to make a servlet work on it.
              The server does function as a Web server as I can run the index.html
              document by entering the URL: http://localhost:7001/index.html
              I am pasting the contents of weblogic.properties file below to get the
              person who is willing to help me started.
              The machine I have is a Pentium III with Windows 2000 Professional on it.
              It's a home machine and the WebLogic server is the freely downloadable
              version. I am using it to prepare for a potential contract work.
              I have managed to modify setEnv.cmd file and have managed to compile the
              SqlServlet.java, which is an example servlet. Neither this particular
              servlet nor a HelloWorld type of very basic servlet I have written are
              recognized by the server.
              As you can see from my weblogic.properties file (pasted at the end of this
              post), the SqlServlet has been registered. I have also uncommented the lines
              to allow for the following type of URL:
              http://localhost:7001/servlet/myServlet
              Thanks!
              Anjum Jaleel
              CONTENTS OF MY weblogic.properties file
              # THE WEBLOGIC PROPERTIES FILE
              # This file, which conforms to the java.util.Properties file
              # definition, configures your WebLogic products. You cannot run
              # WebLogic Server without setting required configuration properties in this
              # file. Required properties are marked and appear first in the file.
              # Details on each entry and important information about configuration
              # and security are documented on our website. Please go to:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # for full instructions on how to edit this file.
              # You do not need to include properties in this file unless you want to
              # change the default, embedded property. Some properties on the
              # AdminProps page are not listed here because the default property
              # is being used. You can change the default by adding the property and
              # its value to this file.
              # You cannot set weblogic.system.home in this file, since the WebLogic
              Server
              # must know where home is in order to retrieve this file. You can
              # change WebLogic home on the command line when you start the
              # WebLogic Server.
              # CLUSTER USERS: Note that the (shared) per-cluster properties file should
              # contain most all of the properties in this file. The only properties
              # that potentially belong in a per-server properties file for a server
              # running in a cluster are the registration (startup class) of pinned
              # RMI objects, and a few tuning properties that may be different for
              # servers in the cluster, depending upon hardware and memory. If you use
              # a per-server properties file, please REMOVE all properties except those
              # that are specifically required in the per-server properties file. You
              # can find specific notes on clusters by searching through this file for
              # "CLUSTER USERS".
              # The way this file is organized:
              # Core properties (includes REQUIRED and RECOMMENDED)
              # Core system properties
              # Core security-related properties
              # Core security-related properties for SSL
              # Core HTTPD administrative properties
              # Optional properties
              # Administrator properties
              # System properties
              # System startup files
              # System shutdown files
              # Security-related properties for Workspaces
              # Jolt for WebLogic properties
              # WebLogic Enterprise Connectivity properties
              # WebLogic File properties
              # WebLogic JMS demo properties
              # WebLogic RMI demo properties
              # WebLogic EJB demo properties
              # WebLogic XML demo properties
              # WebLogic ZAC demo properties
              # HTTPD administrative properties
              # WebLogic JDBC driver properties
              # WebLogic JDBC connection pool management
              # WebLogic demo connection pool
              # WebLogic HTTP Servlet properties
              # Proxy servlet registration
              # Classpath servlet registration
              # File servlet registration
              # ServerSideInclude servlet registration
              # PageCompileServlet (used by JHTML)
              # JSPServlet (used by JSP)
              # ServletServlet registration
              # Servlet reload properties
              # Servlet ACLs
              # WebLogic JSP properties
              # WebLogic JHTML properties
              # WebLogic RMI over IIOP properties
              # User-written and demo servlet registrations
              # CORE PROPERTIES
              # You should set these before you start the WebLogic Server the first time.
              # If you need more instructions on individual properties in this
              # section, check the same section in the Optional Properties, where
              # we've left the long explanations. Or, better yet, go to our
              # website and read all about properties, at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # CORE SYSTEM PROPERTIES
              # TCP/IP port number at which the WebLogic Server listens for connections
              weblogic.system.listenPort=7001
              # CORE SECURITY-RELATED PROPERTIES
              # Read important information about security at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # REQUIRED: The system password MUST be set in order to start the
              # WebLogic Server. This password is case-sensitive, at least 8 characters.
              # The username for the privileged user is ALWAYS "system".
              # This username and password also includes httpd access (see
              # HTTPD properties below).
              weblogic.password.system=lovkako1
              # RECOMMEND Set to 'everyone' if HTTPD is enabled
              weblogic.allow.execute.weblogic.servlet=everyone
              # Set individual ACLs to restrict access to HTTP-related resources,
              # such as the Administration servlets.
              # To make your own servlets generally available, follow this
              # pattern (provide a weblogic.allow.execute) for your packages and
              # set ACLs as appropriate.
              # CORE SECURITY-RELATED PROPERTIES FOR SSL
              # Read important information about SSL at:
              # http://www.weblogic.com/docs51/classdocs/API_secure.html
              # Enable SSL
              # (default if property not defined is false)
              weblogic.security.ssl.enable=true
              # SSL listen port
              weblogic.system.SSLListenPort=7002
              # Servlets for SSL
              # Authentication servlet for creating tokens for applets
              weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
              ervlet
              # Limits number of unclaimed stored tokens
              weblogic.security.certificateCacheSize=3
              # Capture CA root of client servlet
              weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
              # Certificates for SSL
              # Name of acceptable CA roots
              # For client authentication change value to a valid .pem file
              #weblogic.security.clientRootCA=SecureServerCA.pem
              # Server certificates for SSL
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              # registration for certificate generator servlet
              weblogic.httpd.register.Certificate=utils.certificate
              weblogic.allow.execute.weblogic.servlet.Certificate=system
              # CORE HTTPD ADMINISTRATIVE PROPERTIES
              # True permits the HTTPD to run (default)
              # Uncomment this property to disable HTTPD
              weblogic.httpd.enable=true
              # If authentication is required, add username/password for each user
              # who will be included in an ACL, as in this commented-out example:
              #weblogic.password.peter=#8gjsL4*
              # OPTIONAL PROPERTIES
              # These properties affect the behavior of the WebLogic Server.
              # You only need to set these properties if you want
              # to change the default setting, which is the property shown.
              # ADMINISTRATOR PROPERTIES
              # Administrator properties are optional information properties,
              # particularly useful for clusters.
              #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
              94104
              #weblogic.administrator.name=Joe Administrator
              #weblogic.administrator.phone=1 415 555 1234
              # SYSTEM PROPERTIES
              # System properties in this section are set to system defaults
              # Performance pack. The shared library must be accessible from your
              # PATH (NT) or from your shared library path (UNIX; the name of the
              # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              weblogic.system.nativeIO.enable=true
              # Outputs logging information to the console as well as to the log file
              weblogic.system.enableConsole=true
              # Sets the directory or URL for the WebLogic Admin help pages
              # The help pages are shipped in the "docs/adminhelp" directory, in the
              # default document root in public_html
              weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
              p/
              # If you prefer to access the most recent help pages, you can do so online
              # by commenting out the previous property and uncommenting this one:
              #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
              # Properties for tuning the server's performance
              # Number of WebLogic Server execute threads.
              weblogic.system.executeThreadCount=15
              # Other optional system properties
              # Limits size of weblogic.log (in K) and versions old log
              weblogic.system.maxLogFileSize=1024
              # Adjust minimum length of password
              weblogic.system.minPasswordLen=8
              # UNIX only: If running on port 80 on UNIX, enable the setUID program
              #weblogic.system.enableSetUID=false
              # UNIX only: Unprivileged user to setUID to after starting up
              # WebLogic Server on port 80
              #weblogic.system.nonPrivUser=nobody
              # CLUSTER-SPECIFIC PROPERTIES
              # Cluster-specific properties in this section are set to system defaults.
              # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              # in the per-cluster properties file ONLY.
              # Time-to-live (number of hops) for the cluster's multicast messages
              # (default 1, range 1-255).
              #weblogic.cluster.multicastTTL=1
              # Sets the load-balancing algorithm to be used between
              # replicated services if none is specified. If not specified,
              # round-robin is used.
              #weblogic.cluster.defaultLoadAlgorithm=round-robin
              # SERVER-SPECIFIC CLUSTER PROPERTIES
              # Cluster-related properties in this section are set to system defaults.
              # CLUSTER USERS: Note that these server-specific cluster-related properties
              # should be set in the per-server properties file ONLY.
              # Sets the weight of the individual server for the weight-based
              load-balancing.
              # Range is 0 - 100.
              # Larger numbers increase the amount of traffic routed to this server.
              #weblogic.system.weight=100
              # SYSTEM STARTUP FILES - Examples
              # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              # objects should be registered in the per-server properties file.
              # All other startup classes should be registered in the per-cluster
              # properties file.
              # For more info on writing and using startup file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a startup class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.startupClass.[virtual_name]=[full_pathname]
              # Add arguments for the startup class
              #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/StartupQuery.java
              #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
              #weblogic.system.startupArgs.doquery=\
              # query=select * from emp,\
              # db=jdbc:weblogic:pool:demoPool
              # SYSTEM SHUTDOWN FILES - Examples
              # For more info on writing and using shutdown file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a shutdown class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
              # Add arguments for the shutdown class
              #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/ShutdownTest.java
              #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
              #weblogic.system.shutdownArgs.ShutdownTest=\
              # outfile=c:/temp/shutdown.log
              # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              # For backward compatibility, the following entries disable Access
              # Control on Workspaces
              weblogic.allow.read.weblogic.workspace=everyone
              weblogic.allow.write.weblogic.workspace=everyone
              # JOLT FOR WEBLOGIC PROPERTIES
              # These properties configure a BEA Jolt connection pool for use with
              # the simpapp and bankapp examples, and register a servlet for use with
              # with the simpapp example. The default server address provided here
              # points to a public TUXEDO server that is hosted by BEA for use with
              # this example.
              # Servlet registration for simpapp example:
              #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
              t
              # Pool creation and cleanup
              # note this example is set up to work with the public
              # demo TUXEDO server available from BEA's website:
              #weblogic.system.startupClass.demojoltpoolStart=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
              #weblogic.system.startupArgs.demojoltpoolStart=\
              # poolname=demojoltpool,\
              # appaddrlist=//beademo1.beasys.com:8000,\
              # failoverlist=//beademo1.beasys.com:8000,\
              # minpoolsize=1,\
              # maxpoolsize=3
              #weblogic.system.shutdownClass.demojoltpoolStop=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
              #weblogic.system.shutdownArgs.demojoltpoolStop=\
              # poolname=demojoltpool
              # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
              # The registrations enable a BEA IIOP connection pool and
              # register servlets for use with the simpapp and university examples.
              # Configure for your environment and uncomment to use.
              # Uncommenting these properties requires WebLogic Enterprise Connectivity
              # and an operating WebLogic Enterprise Server.
              # Servlet registration for simpapp servlet example
              #weblogic.httpd.register.SimpappServlet=\
              # examples.wlec.servlets.simpapp.SimpappServlet
              #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
              # Servlet registration for simpapp EJB example
              # (You'll need to add the wlec_ejb_simpapp.jar to the
              # weblogic.ejb.deploy property in this file.)
              #weblogic.httpd.register.ejbSimpappServlet=\
              # examples.wlec.ejb.simpapp.ejbSimpappServlet
              #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
              # Pool creation and cleanup for the simpapp example
              #weblogic.CORBA.connectionPool.simplepool=\
              # appaddrlist=//wlehost:2468,\
              # failoverlist=//wlehost:2468,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # domainname=simpapp
              # Servlet registration for university Servlet example:
              #weblogic.httpd.register.UniversityServlet=\
              # examples.wlec.servlets.university.UniversityServlet
              #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
              # Pool creation and cleanup for the University example:
              #weblogic.CORBA.connectionPool.Univpool=\
              # appaddrlist=//wlehost:2498,\
              # failoverlist=//wlehost:2498,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # apppassword=wlepassword,\
              # domainname=university
              # WEBLOGIC FILE PROPERTIES
              # Maps a volume name to a path, for client file read/write
              #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              # WEBLOGIC JMS DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL JMS deployment should be done in the
              # per-cluster properties file ONLY.
              # You set up a JDBC connection pool if you want persistent messages
              # (including durable subscriptions). To use JMS and EJBs in the same
              # transaction, both must use the same JDBC connection pool. Uncomment
              # the following property to use the default JDBC connection pool
              # 'demo', which is defined in the Demo connection pool section of this file.
              #weblogic.jms.connectionPool=demoPool
              # The JMS Webshare example demonstrates how the ClientID for a
              # durable subscriber is configured in the connection factory:
              #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
              #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
              #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
              #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
              # The JMS trader example shows how to use JMS with an EJB. In addition
              # to uncommenting the following properties, you must also set up and
              # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
              # ejb_basic_statelessSession.jar to try out this JMS example:
              #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
              #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
              #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
              #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
              # Registers the underlying servlet
              #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
              # These properties are used with the ServerReceive JMS example,
              # which demonstrates how to establish a JMS message consumer
              # in a startup class:
              #weblogic.system.startupClass.serverReceive=\
              # examples.jms.startup.ServerReceive
              #weblogic.system.startupArgs.serverReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              # These properties are used with the PoolReceive JMS example,
              # which demonstrates how to establish a pool of JMS message consumers
              # in a startup class:
              #weblogic.system.startupClass.poolReceive=\
              # examples.jms.startup.PoolReceive
              #weblogic.system.startupArgs.poolReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
              # WEBLOGIC RMI DEMO PROPERTIES
              # CLUSTER USERS: Note that pinned RMI objects should be registered
              # in the per-server properties file ONLY. All other RMI startup
              # classes should be registered in the per-cluster properties file.
              # Remote classes registered at startup after the pattern:
              #weblogic.system.startupClass.[virtualName]=[fullPackageName]
              # These examples can be compiled to see RMI in action. Uncomment to use:
              #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
              #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
              #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
              # WEBLOGIC EJB DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              # per-cluster properties file ONLY.
              # See WebLogic Demo Connection Pool below for a connection pool
              # to use with these examples.
              # Deploys EJBeans. Uncomment the appropriate lines below and
              # modify DBMS-related info and paths to match your particular installation:
              #weblogic.ejb.deploy=\
              # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
              # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
              # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
              # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
              # g:/weblogic/myserver/ejb_subclass.jar, \
              # g:/weblogic/myserver/jolt_ejb_bankapp.jar
              # Servlet used by the EJB basic beanManaged example
              # Uncomment to use:
              #weblogic.httpd.register.beanManaged=\
              # examples.ejb.basic.beanManaged.Servlet
              # Add a list of users (set the password with
              weblogic.password.[username]=XXX)
              # to set an ACL for this servlet:
              #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
              #weblogic.password.user1=user1Password
              #weblogic.password.user2=user2Password
              # WEBLOGIC XML DEMO PROPERTIES
              # These properties are required to run the XML examples.
              # Uncomment to use.
              # CLUSTER USERS: Note that ALL servlets should be set up
              # in the per-cluster properties file ONLY.
              #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
              # BizTalk example properties
              #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
              #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
              #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
              dapter
              #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
              # WEBLOGIC ZAC DEMO PROPERTIES
              # These registrations enable the ZAC Publish Wizard.
              weblogic.zac.enable=true
              # Set the publish root for a WebLogic Server. Edit and
              # uncomment to use.
              #weblogic.zac.publishRoot=g:/weblogic/zac
              # Set an ACL for each package you publish. The [name] is
              # the "Package name" you assign in the ZAC Publish Wizard.
              # Publish a package, edit this property, and uncomment to use.
              #weblogic.allow.read.weblogic.zac.[name]=[user list]
              #weblogic.allow.write.weblogic.zac.[name]=system
              # HTTPD ADMINISTRATIVE PROPERTIES
              # Enables logging of HTTPD info in common log format and
              # sets the log file name (default is "access.log" in "myserver")
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              weblogic.httpd.enableEvents=false
              # Enables HTTP sessions
              weblogic.httpd.session.enable=true
              # Sets an optional cookie name. The default name is "WebLogicSession".
              # Prior to version 4.0, the default was "TengahSession". To make
              # this backward compatible with cookies generated from previous
              # installations, you should set this property to "TengahSession".
              # Uncomment this line and set this to any string of your choice,
              # or comment out this property to use the default.
              #weblogic.httpd.session.cookie.name=WebLogicSession
              # MIME types
              weblogic.httpd.mimeType.text/html=html,htm
              weblogic.httpd.mimeType.image/gif=gif
              weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
              weblogic.httpd.mimeType.application/pdf=pdf
              weblogic.httpd.mimeType.application/zip=zip
              weblogic.httpd.mimeType.application/x-java-vm=class
              weblogic.httpd.mimeType.application/x-java-archive=jar
              weblogic.httpd.mimeType.application/x-java-serialized-object=ser
              weblogic.httpd.mimeType.application/octet-stream=exe
              weblogic.httpd.mimeType.text/vnd.wap.wml=wml
              weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
              weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
              weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
              weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
              # In seconds, the keep-alive for HTTP and HTTPS requests
              weblogic.httpd.http.keepAliveSecs=60
              weblogic.httpd.https.keepAliveSecs=120
              # WEBLOGIC JDBC DRIVER PROPERTIES
              # Enables JDBC driver logging and sets the file name for the log
              # The weblogic.jdbc.logFile is placed in the per-server
              # directory (default is "myserver")
              weblogic.jdbc.enableLogFile=false
              weblogic.jdbc.logFileName=jdbc.log
              # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
              # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
              # in the per-cluster properties file ONLY.
              # For creating JDBC connection pools. This example shows a connection
              # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
              # to use 4 JDBC connections (with a potential for up to 10 connections,
              # incremented by two at a time, with a delay of 1 second between each
              # attempt to connect to the database), to an Oracle database server called
              # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
              # connections are dropped from the pool until only 4 connections remain
              open.
              # Every 10 minutes, any unused connections in the pool are tested and
              # refreshed if they are not viable.
              #weblogic.jdbc.connectionPool.oraclePool=\
              # url=jdbc:weblogic:oracle,\
              # driver=weblogic.jdbc.oci.Driver,\
              # loginDelaySecs=1,\
              # initialCapacity=4,\
              # maxCapacity=10,\
              # capacityIncrement=2,\
              # allowShrinking=true,\
              # shrinkPeriodMins=15,\
              # refreshMinutes=10,\
              # testTable=dual,\
              # props=user=SCOTT;password=tiger;server=DEMO
              # Get more details on each argument for this property in the
              # Administrators Guide on setting properties at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # Set up ACLs for this connection pool with the following:
              #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
              # guest,joe,jill
              #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
              # joe,jill
              #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

    Problem Resolved!
              I found out that I had 'http' instead of 'httpd' in the statement where I
              registered my servlet, SqlServlet.
              Now, I am having difficulty with hot deployment. The server is returning
              error 404.
              

  • The remote server returned an error: (401) Unauthorized

    We are attempting to upload a file to SharePoint on Office 365 and get the following error:
    The remote server returned an error: (401) Unauthorized.
    We also tried using NetworkCredentials and that got the following error: The remote server returned an error: (404) Not Found.
    The code is shown below.
    Any idea on to fix this error?
    public
    void uploadDocument(string
    siteurl, string username,
    SecureString securepassword,
    string domain,
    string filestreamPath =
    "NewDocument.docx",
    string serverRelativeUrl =
    "/Shared Documents/NewDocument.docx")
    ClientContext context =
    new
    ClientContext(siteurl);
            //context.Credentials = new NetworkCredential(username, securepassword, domain);
    context.Credentials = new
    SharePointOnlineCredentials(username, securepassword);
    using (FileStream
    fileStream =
    new
    FileStream(filestreamPath,
    FileMode.Open))
    ClientOM.File.SaveBinaryDirect(context,
    serverRelativeUrl, fileStream, true);

    Yes, it has access.  In fact, it has no problem getting the site properties using the code below.  It is just when I am uploading a file that the error occurs.
    public Web getProperties(string
    siteurl, string username,
    SecureString securepassword)
    Web web = null;
    // Starting with ClientContext, the constructor requires a URL to the
    // server running SharePoint.
    ClientContext context = new ClientContext(siteurl);
    // The SharePoint web at the URL.
    web = context.Web;
    // We want to retrieve the web's properties.
    context.Load(web);
    // Execute the query to the server.
    context.Credentials = new SharePointOnlineCredentials(username, securepassword);
    context.ExecuteQuery();
    return web;

  • Error 404 in 11g

    Hi Friends,
    Im working in ADF 11g. I have a jspx page and I wonder why often I get the following error continously inspite of killing all Server processes.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Help me in finding the issue.
    Thanks,
    User

    Lemme tell you..
    To run a .jspx page we have to start the server whcih gets automatically started once we say Run.
    So the ouput will be that error message. I tried killing the process and running it again. It displays the same even the Server is on.
    Thanks,
    User

  • Exchange Server 2003 authenciation error.Pls help

    Hi all,
    I use the following codes to connet Exchange Server 2003, but errors occurs.Can anybody help me?
    String host = (String)map.get("host");
    Integer port = (Integer)map.get("port");
    String username = (String)map.get("username");
    String password = (String)map.get("password");
    Properties props = new Properties();
    Session session = Session.getDefaultInstance(props, null);
    if (LOG.isDebugEnabled()) {
    session.setDebug(true);
    Store store = session.getStore(this.getProvider());
    store.connect(host, port, username, password);
    DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc]
    DEBUG: mail.imap.fetchsize: 16384
    DEBUG: mail.imap.statuscachetimeout: 1000
    DEBUG: mail.imap.appendbuffersize: -1
    DEBUG: mail.imap.minidletime: 10
    DEBUG: trying to connect to host "xxx", port 143, isSSL false
    * OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (xxx.xxx.local) ready.
    A0 CAPABILITY
    * CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS MAILBOX-REFERRALS NAMESPACE LITERAL+ UIDPLUS CHILDREN AUTH=NTLM
    A0 OK CAPABILITY completed.
    IMAP DEBUG: AUTH: NTLM
    DEBUG: protocolConnect login, host=xxx, user=tester1, password=<non-null>
    DEBUG NTLM: type 1 message: suppliedDomain: ; suppliedWorkstation: Concord.xxx.local
    DEBUG NTLM: type 1 message length: 54
    A1 AUTHENTICATE NTLM
    +
    TlRMTVNTUAABAAAAACAAAAAAAAAAAAAAFgAWACAAAABDT05DT1JELkdFQVJURUtTLkxPQ0FM
    A1 NO Logon failure: unknown user name or bad password.
    16:07:01,951 pool-11-thread-1 ERROR MailMessageActionService: - Logon failure: unknown user name or bad password.

    JavaMail 1.4.3 added support for NTLM authentication. Normally I would expect that the
    same username and password would work with any authentication mechanism that's
    supported by the server, but that doesn't seem to be the case here.
    You can disable ntlm authentication by setting the session property "mail.imap.auth.ntlm.disable" to "true".

Maybe you are looking for

  • Can't get sound through my speakers in Logic.

    So for an assignment I recorded loads of stuff in the studios at uni and come back to mix it on Logic on my laptop and I can't seem to get any sound out from my speakers through logic. Speakers are working cause I'm listening to iTunes. I don't know

  • Read performance of a generically typed hashed table

    Hi,     I'm curious to know the how the read performance of a hashed table will be affected in the following scenario. I have a class with many static attributes of hashed table type. All these hashed tables have one thing in common. They have a fiel

  • Coherence-eclipselink.jar available in TopLink11.1.1.0.1 not in 11.1.1.1.0

    Hi, I am following the link : [ http://www.oracle.com/technology/products/ias/toplink/doc/11110/grid/tlgug001.htm|http://www.oracle.com/technology/products/ias/toplink/doc/11110/grid/tlgug001.htm] for integrating coherence with Oracle Toplink. The ja

  • Please help !!! change character_set of database

    hi friends i have a problem i create a database with this character set --> we8iso8859p1 now i need to change the character set to ar8mswin1256. i donot want to create a new database. is there any way? thanks. shoja.

  • Do I need to change Imaq Create VI or related VIs for a 1394a firewire camera?

    I have a program to acquire images from a Zeiss axiocam MR2 that has a PCI framegrabber.  Now I am trying to acquire images from one of their firewire cameras using the same program (while swapping the dll functions calls specific for the firewire ca