I'm getting no error using float in cldc1.0 with wtk2.2?

I'm getting no error using float in cldc1.0 with wtk2.2?

ravikumar.tj wrote:
Please set wtk settings as cldc1.0 and midp1.0.
Create a subclass of MIDlet as-
public void startApp()
float f;
double d;
Press Create Package, Jar and Jad files are getting generated successfully.
If Cldc1.0 doesn't support float, I must get Compile error, isn't??That's ok, but just because you're not doing anything with those variables so the compiler ignores them.
This should give you a preverify error:
     protected void startApp() throws MIDletStateChangeException {
          double d=0.5;
     }

Similar Messages

  • I am trying to install iTunes on my PC, but I get this error: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor." Help!

    I am trying to install iTunes on my PC (using Windows 8.1), but I get this error: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor." The iTunes file (64-bit) I am trying to install, is named "iTunes64Setup.exe". What seems to be the problem? Help!

    Hey madnest,
    Thanks for the question. After reviewing your post, it sounds like you are having difficulty installing iTunes in Windows. I would recommend that you read this article, it may be able to help you resolve or isolate the issue.
    Issues installing iTunes or QuickTime for Windows
    Thanks for using Apple Support Communities.
    Have a nice day,
    Mario

  • No way to publish a workflow, I get this error: System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.ScopeInactiveException: Scope ... is not in an active state. Its current state is 'Unregistering'

    Hi,
    I'm using Project Server 2013 and I'm not able to publish a workflow in SharePoint Designer 2013, I get this error:
    System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.ScopeInactiveException: Scope '/SharePoint/default/d7feb9ea-ccb2-4ec3-8f89-2a45b6cf3777' is not in an active state. Its current
    state is 'Unregistering'. HTTP headers received from the server - ActivityId: c47ef567-8c54-4ae0-9a1a-1e4fb51320d8. NodeId: TestServer. Scope: /SharePoint/default/d7feb9ea-ccb2-4ec3-8f89-2a45b6cf3777. Client ActivityId : c6e5979c-20f8-e042-1f9d-2cb2a25d7f9e.
    ---> System.Net.WebExceptio
    The thing is that I transferred the databases from a Prod.Env. to the Test Env. and from that moment on the Test Env. stopped working (only workflows), then I
    was thinking that maybe the workflow is not working in the Test Environment because when I transferred the databases from Prod Env to Test Env I didn’t transfer the databases related to workflow, I only transferred:
    WSS_Content
    PWA_ServiceDB
    But I didn’t transfer:
    SBGatewayDatabase
    SBManagementDB
    SBMessageContainer01
    WFInstanceManagementDB
    WFManagementDB
    WFResourceManagementDB
    I didn’t transfer them because, before, when I transferred DB’s in version 2010, these DB’s were not needed, as the workflows were done using another method.
    So, I tried to create a new workflow in the Test Env. but there is no way, I always get that error.
    I've tried to Register again the workflow, and the result looks ok, but it doesn't solve the problem:
    Register-SPWorkflowService
    –SPSite "http://whatever/PWA"
    –WorkflowHostUri "http://TestServer:12291"
    –AllowOAuthHttp -Force
    Do you know how to solve this issue or have an idea to give me some light?
    Thank you for your help and regards,
    José Espases

    Looks like you haven't defined the WF scope or the site where you are trying to deploy the workflow to isn't included in the scope
    Check this article
    http://fangdahai.blogspot.in/2013/04/on-premise-windows-workflow-server.html
    Thanks | epmXperts | http://epmxperts.wordpress.com

  • When trying to sync my iPad to my computer, I get the error "the iPad is synced with another iTunes library.

    When trying to sync my iPad to my computer, I get the error "the iPad is synced with another iTunes library. An iPad can be synced with only one iTunes library at a time." I only have one iTunes account, so I am a little confused. If I select the option to "Transfer Purchases, I get an error message that says "Attempting to copy to the disk failed. You do not have enough access privileges for this operation."
    Any suggestions is appreciated.

    Have you synced to this computer before?

  • I use floating time zone with all of my iCal entries.  But then the times of the entries do not print when printing month view.  Is there a fix for this?

    I use floating time zone with all of my iCal entries.  But then the times of the entries do not print when printing month view.  Is there a fix for this?

    Sorry to have repeated this question as if I were answering it.  Just a mistake.  I'm just now learning how to use this site.

  • I get an error message when installing itunes with windows 8, error message is error occured while attempting to create the directory C:\program file(x86)\common files\apple\mobile device support\sync services\schemas\outlook.syncschema

    I keep getting an error message when installing iTunes with windows 8

    See the second box in Troubleshooting issues with iTunes for Windows updates.
    tt2

  • Experiencing trouble syncing with the 10.3 version of iTunes on my Windows Vista machine. Have uninstalled all Apple software twice, reinstalled and continue to get an error 7 message in connection with the Photo Processor. Any other ideas to try?

    Experiencing trouble syncing with the 10.3 version of iTunes on my Windows Vista machine. Have uninstalled all Apple software twice, reinstalled and continue to get an error 7 message in connection with the Photo Processor. Any other ideas to try?

    Hi,
    got it fixed! My Son had both files on his Win7 iTunes installation. Never mind he had no issues whith ths iTunes and iPhone Sync. So I checked my other Win XP PC, where I don't have this problem syncing my ipad, and surprise. Both files do NOT show up on this PC. So I renamed the iTunesPhotoProcessor.exe I found under c:\program file\iTunes and synced again my iPhone and it went through without any error. So the problem might be and unremoved iTunesPhotoProcessor.exe or the missing iTunesPhotoProcessor.dll under the iTunes install root folder and this even if I had checked that the folder was completely removed during iTunes unistall.
    Please try yourselve and just rename the iTunesPhotoProcessor.exe to iTunesPhotoProcessor.exe_ under c:\program file\iTunes or get a copy of the missing iTunesPhotoProcessor.dll and cp to c:\program file\iTunes.

  • When synchig my iphone to my itunes, I get an error message at the end with code 1150.  What is this error code and what does it mean?

    When synching my iphone to my itunes, I get an error message at the end with code 1150.  What is this error code and what does it mean?

    try uninstalling and reinstalling itunes on your computer. here is a link for that http://support.apple.com/kb/HT1925

  • I have been trying to restore my iphone5 with icloud back up. Keep getting an error. Any trouble today with Icloud? what can be happening? (I restored it yesterday to an older back up and it worked perfectly!!)

    I have been trying to restore my iphone5 with icloud back up. Keep getting an error. Any trouble today with Icloud? what can be happening? (I restored it yesterday to an older back up and it worked perfectly!!)

    From your other post on the same subject.
    my iphone not restoring to icloud today. I restored it yersterday to an older copy and worked perfectly...  Any troubles today with ICloud? what should I do?

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • Field is in DB table/alias but I get ORA904 error using it in OBIEE Answers

    Hello, I'm very new at developing with RPD and OBIEE tools, so I'm struggling with something that I thought I did correctly. I added a new field to a database table, and can query it in the database. I added it to the table in RPD Physical layer and I verified that it also now exists in an alias of that table. The physical alias table field is used as a source for a logical column in the presentation layer. Everything looks good in the RPD. But when I try to pull it up in a query in OBIEE Answers I get a 904 error telling me that the column does not exist. I've bounced the servers, dropped cookies and cache, but nothing helps - I still get the error.
    What step could I have missed?
    Thanks in advance!
    Rich

    THank you all for the advice, but it still appears to be a problem. Here's what I tried and the results:
    1. Right-clicked on the new column to do a row count update. As predicted by Gaurav, this also failed with a 904 error.
    2. Verified exact spelling is correct.
    3. Checked the connection pool. THis looks correct, but I will double-check today with one of my co-workers who has more experience with RPD.
    4. Tried querying the column in RPD - this also failed with 904 error.
    5. Checked the LTS within BMM layer and my new field does map back to the alias column
    6. Ran a consistency check and the only errors (warnnings actually) are for a different, unrelated table.
    7. Checked security and it also looks okay, but this is another one I'll double-check later with one of our experts here.
    8. Joins in physical layer and BMM look good
    9. Checked physical column and table in the presentation layer. These also point to the right columns/tables
    10. Selecting the column by itself in analysis fails with 904.
    If anyone can think of something else to consider based on this please advise. One thing I did notice is that in performing the steps above I noticed somewhere (the BMM I think) that the new column I added is at the bottom of the table (last field) and not in the middle as it is in the database. In past experience with other tools this hasn't mattered, but I'm going to see if I can change that and if that has an effect. I'm guessing it won't but I'm running out of ideas!
    Thanks again,
    Rich

  • Getting certificate errors using hotmail

    I'm getting certificate errors intermittently when using hotmail.  This has been happening for the 3 days I've had my Mac.
    Here's the error:
    Safari can't verify the identity of the website "secure.shared.live.com".
    The certificate for this website is invalid.  You might be connecting to a website that is pretending to be "secure.shared.live.com", which could put
    your confidential information at risk.  Would you like to connect to the website anyway?
    It looks like from the specific certificate error, it's a problem with "secure.wlxrs.com" (whatever that means).
    Anyone have any ideas on what this is all about and how to remedy it?
    Message was edited by: john114

    Hi pbwpu,
    Thanks for posting. Are you still having this problem? Can you post a screen shot of the message you're seeing? Give us as much detail as possible and I'm sure we'll be able to help.
    Cheers
    David
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

  • Why can't I update an app on my iPad?  I get an error message saying  redonload unavailable with this apple id because either it was bought by a different user or the item was refunded or cancelled..what can I do?

    I am trying to update apps on my iPad.  We are using family sharing.  My husband has the app on his iPad.  When I try to download, i get the error message and it doesn't look like I have the app on my iPad.  I had it on an older iPad and did cancel the service but now don't have it on this new iPad.  Help.

    Apple are working on it

  • I'm getting this error "sec_error_ocsp_bad_http_response" on several sites with FF 6.0.2 and earlier versions, but not getting the error with IE.

    I've been getting this error on several websites, this is the latest one it just came up on. I got it while trying to sign onto this page.
    I am able to connect using IE 9, Windows 7 Enterprise.

    Under Advanced>Encryption:Certificate>Validation both boxes were checked, to Use OCSP server to validate the certificate and if the connection fails, then to consider the certificate as Invalid.
    I unchecked the second box (consider the cert as invalid) and now I am able to connect to the websites. This is a business computer and I don't surf with it very much (when I do it is to answer IT questions using Google searches) so I'm not too concerned about turning off the validation.
    Thanks for you assistance to both '''cor-el''' and to''' mha007'''.

  • PDF documents have stopped printed in Firefox. I get an error message. No problem with Safari.

    When I try to print a pdf -- either one that I've created or one downloaded from the Internet, I get an error message and the document will not print.

    Firefox finds my home page. When I go somewhere else, I get to offline message. I go and uncheck "Work Offline", but it still does not work. Firefox no longer works for me and I had to go back to Internet Explorer.

Maybe you are looking for