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 :-)
Similar Messages
-
Why do I get certificate errors?
Why am I getting certificate errors for Facebook and other sites? Why am I getting Invalid URLs as well?
It started about 1.5 - 2 months ago. I can go to CNN, yahoo news etc and I get certificate errors for Facebook. It always say something about that Safari can validate certificate for s-static facebook or something like that.
-
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;
} -
I used a link in an email to check the status of a repair from Acer and received the error "customercare.acer.com uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)". I tried going directly to the Acer website, and went to support, then to check case status. I received the same error. I reactivated IE 10 on my OS and had no problems with certificate errors. I use McAfee Antivirus suite from ATT Uverse, but the troubleshooting did not indicate any settings for that, only ESET and Bitdefender.Could you take a look at the certificate details?
If you click "I understand the risks" and "Add Exception", then the "View" button, does it look at all like the attached? I suggest using a new window to compare because when the certificate viewer is open, you cannot switch tabs in the same window.
You can cancel the viewer after checking, you may not want to create an exception until getting further comments. -
New windows 8.1 clients getting certificate error
We are running exchange 2010 and one of our end-users just recently purchased a windows 8.1 laptop. When he tries to connect to exchange using the built-in mail app, he gets the error, "To connect to this account, you need a valid certificate
on this PC. Contact your system administrator for more info"
I searched a lot online and found a suggestion of signing into OWA and exporting the root level certificate, then installling it. I did that, but still receive the error on his machine.
Any suggestions?Hi,
Supplementing a blog for your reference:
Supporting Windows Mail 8.1 in your organization
http://blogs.technet.com/b/exchange/archive/2013/10/18/supporting-windows-mail-8-1-in-your-organization.aspx
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Get certificate error trying to access yahoo mail, and there is no exception to bypass the error.
I am getting a certificate error trying to access https://mail.yahoo.com. Unlike most other certificate errors, there is no option for "I understand the risks" to add an exception for the page, just the following:
mail.yahoo.com uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. (Error code: sec_error_unknown_issuer)
I tried setting the proxy to "no proxy" under Advanced settings, as well as clearing all cookies and other cache history. Did not resolve the problem. I cannot access my email.hello, which security program is running on your computer?
-
Certificate error using webauth on guest wifi
I am trying to setup a guest wifi. We have our custom page package loaded and it looks great with our graphics, logo. Basically you have to check a box and click accept to the terms of service, and then it forwards you through to VLAN 12 in this case, which is directed to an untangle software based firewall / router with its own outside IP address.
The issue is that when you initially join the wireless network, the page at 1.1.1.1/login.htm throws a certificate error and you have to continue anyway (Internet Explorers language).
Does this mean we need to put our wildcard certificate on it for our *.domain.com (GoDaddy signed) or does it need another kind of certificate? What format would it need to be in (I have a pfx but can convert it if need be).
We are not passing any credentials, so it doesn't NEED to be https, so under Management > HTTP-HTTPS I changed WebAuth SecureWeb to Disabled. However when doing this, WebAuth is still putting https://1.1.1.1 and I get a page cannot be displayed. I take the s out of https and then the webauth page works.
So two things here, how could I just use it in http, or if preferred, what format and what kind of certificate needs to make https work in webauth? This is primarily for vendors that visit, or guests in our waiting lobby with their tablets or smartphones.
The WLC is a 5508 running 7.4.121.0.I also tried this site as well:
http://www.packethead.net/2013/08/05/cisco-wlc-wireless-lan-controller-certificate-install-mac-os-x/
I tried it command line, and it tftp's fine in all instances above but I get:
TFTP Webauth cert transfer starting.
TFTP receive complete... Installing Certificate.
Error installing certificate.
Might have to open a case with tac if this doesn't work.
I have openssl 1.0.1j is that maybe a bad version? also every time I run it it says WARNING: can't open config file: /usr/local/ssl/openssl.cnf
Well of course not, that is a *nix based bath and this is the 64-bit windows version.
What I can get is a download from go daddy and the wildcard cert is already generated. I cannot submit a new cert request. We have this key and I've tried different ways of converting it with OpenSSL, I've imported it to windows and in the mmc for certificates exported in various formats. Nothing will work with this WLC. -
Hi
I'm looking for a solution that I can't seem to find. I have an Exchange 2010 server running in a dot local domain (domainname.local), so my SSL certificate is installed using the servers external email DNS name. email.mycompany.com
I have followed the instructions to resolve this on the Exchange server, implemented the changes so autodiscovery sees the server as email.mycompany.com. This works great for my Outlook 2007 users. The downside is that none of my Outlook 2013
clients can access their email without the certificate error server name mismatch.
I know Outlook 2013 has tighter security but I need to get rid of these cert errors, any thoughts out there?Hi,
Since both your Outlook 2007 users and Outlook 2013 users are using Exchange 2010 with the same server configuration, it should be working in both Outlook client version.
Please restart your IIS service by running IISReset /noforce from a Command Prompt window in Exchange to have a try. In Outlook, please re-create a Outlook profile to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support -
Not on an enterprise server. I'm using Google sync for my calendar. I get repeated Certificate errors. When I choose to TRUST them, I get messages back which say the certificates cannot be stored do to the IT policy.
What IT Policy? I just got the phone yesterday and am not associated with a company.
grrrrFind a friend with a PC, you can use for a few hours.
I would recommend Desktop Manager, version 6. Download Desktop Manager from here:
https://www.blackberry.com/Downloads/entry.do?code=A8BAA56554F96369AB93E4F3BB068C22
Use Desktop Manager to backup your BlackBerry first. If you don't already, you should do this on your own Mac Desktop for Blackberry as well.
See the link below, for the download and simple installation instructions.
1. Download the OS file to the PC then install it to the PC by running (double clicking) the file you downloaded.
https://www.blackberry.com/Downloads/entry.do?code=06997F04A7DB92466A2BAA6EBC8B872D
2. Go to c:\program files\common files\research in motion\apploader and delete the file named "vendor.xml."
3. Plug in BB and double click on "Loader.exe." It's located in the same place as the above vendor.xml file.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
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
DaveDavid,
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!
RichTHank 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 -
I keep getting certificate errors even on apple pages
I have a macbook pro 13 retina disply (OS10) and no matter what page I want to pull up safari give me the message that safari can't verrify the identity of the website. when i look at the certificate it says the the certificate is not yet valid. I have the time set correctly on the computer. This also happens when trying to use the apple website. As a result, i am using my ipad to write this problem. Any suggestions would be appreciated.
This could be a complicated problem to solve, as there are several possible causes for it.
Back up all data, then take each of the following steps that you haven't already taken. Stop when the problem is resolved.
Step 1
From the menu bar, select
▹ System Preferences... ▹ Date & Time
Select the Time Zone tab in the preference pane that opens and check that the time zone matches your location. Then select the Date & Time tab. Check that the data and time shown (including the year) are correct, and correct them if not.
Check the box marked
Set date and time automatically
if it's not already checked, and select one of the Apple time servers from the menu next to it.
Step 2
Triple-click anywhere in the line below on this page to select it:
/System/Library/Keychains/SystemCACertificates.keychain
Right-click or control-click the highlighted line and select
Services ▹ Show Info
from the contextual menu.* An Info dialog should open. The dialog should show "You can only read" in the Sharing & Permissions section.
Repeat with this line:
/System/Library/Keychains/SystemRootCertificates.keychain
If instead of the Info dialog, you get a message that either file can't be found, reinstall OS X.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. Open a TextEdit window and paste into it by pressing command-V. Select the line you just pasted and continue as above.
Step 3
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
In the upper left corner of the window, you should see a list headed Keychains. If not, click the button in the lower left corner that looks like a triangle inside a square.
In the Keychains list, there should be items named System and System Roots. If not, select
File ▹ Add Keychain
from the menu bar and add the following items:
/Library/Keychains/System.keychain
/System/Library/Keychains/SystemRootCertificates.keychain
Open the View menu in the menu bar. If one of the items in the menu is
Show Expired Certificates
select it. Otherwise it will show
Hide Expired Certificates
which is what you want.
From the Category list in the lower left corner of the window, select Certificates. Look carefully at the list of certificates in the right side of the window. If any of them has a blue-and-white plus sign or a red "X" in the icon, double-click it. An inspection window will open. Click the disclosure triangle labeled Trust to disclose the trust settings for the certificate. From the menu labeled
Secure Sockets Layer (SSL)
select
no value specified
Close the inspection window. You'll be prompted for your administrator password to update the settings.
Now open the same inspection window again, and select
When using this certificate: Use System Defaults
Save the change in the same way as before.
Revert all the certificates with non-default trust settings. Never again change any of those settings.
Step 4
Select My Certificates from the Category list. From the list of certificates shown, delete any that are marked with a red X as expired or invalid.
Export all remaining certificates, delete them from the keychain, and reimport. For instructions, select
Help ▹ Keychain Access Help
from the menu bar and search for the term "export" in the help window. Export each certificate as an individual file; don't combine them into one big file.
Step 5
From the menu bar, select
Keychain Access ▹ Preferences... ▹ Certificates
There are three menus in the window. Change the selection in the top two to Best attempt, and in the bottom one to CRL.
Step 6
Triple-click anywhere in the line of text below on this page to select it:
/var/db/crls
Copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.
A folder named "crls" should open. Move all the files in that folder to the Trash. You’ll be prompted for your administrator login password.
Restart the computer, empty the Trash, and test.
Step 7
Triple-click anywhere in the line below on this page to select it:
open -e /etc/hosts
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. A TextEdit window should open. At the top of the window, you should see this:
# Host Database
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
If that's not what you see, post the contents of the window. -
Getting certificate error while open the hierarchy of reporting services.
Hi All,
I am facing problem in reporting server in SCCM 2012 SP1 and the OS is windows server 2012 R2. All the things are working fine but when I have installed the reporting feature reports were not showing in SCCM monitoring node.
Then I tried to open reporting service in sql server which is a remote system and the OS is win20212 R2 Server reporting service are connected properly but when I am going to expand or right click on hierarchy blow error message is showing. Please help me
out for this.
master Plz help me out for this.
Thanks
Animesh Shankar.Have you checked the certificate of your SQL?
http://sccmfaq.files.wordpress.com/2013/06/report-builder-02.png
www.sccmfaq.ch -
Errors using hotmail in Firefox
The hotmail account opens without any problem, however, while going thru the mail, none of the buttons like new, forward move to etc function, infact they do not get underlined when the pointer is brought on them, thus I am unable to move, delete or forward any mail.
I do not face this problem with Google chrome or IE
I have also downloaded the latest version of Firefox i.e. 7.0.1
Plz helpI had the same problem. All software up to date. Firefox 12.0. What fixed it for me was disabling my Foxit Reader plugin. I recently updated Foxit Reader and the plugin in Firefox shows it as "Foxit Reader Plugin for Mozilla 2.2.1.417".
Disabled it and now all is fine. Problem seems to be with Foxit...for me at least. -
L675D-S7016 (PSK3JU) gets FreeDOS errors using CD method to install BIOS version 1.50
I downloaded sk3jv150.exe from Toshiba's support site and followed the instructions to create a bootable CD to flash the BIOS. In fact, I have created the boot CD several times using different programs on this laptop and even on two other PCs but have had no success.
Whenever I boot from the CD, FreeDOS starts and the following error messages appear:
-InitDiskWARNING: using suspect partition Pri:1 FS 01 with calculated values 1-0-1 instead of 0-1-1
WARNING: using suspect partition Pri:1 FS 01: with calculated values 255-0-63 instead of 1-0-63
C:HD1, Pri[1],CHS= 1-0-1, start= 0MB size=7M
This laptop came with Windows 7 Home Premium 64-bit and I purchased it new in the Fall of 2010.
Any ideas?After you receive the error you should be at a C: prompt. Enter BIOS.BAT and hit enter. This should lauch the BIOS flash application.
Maybe you are looking for
-
What causes a slow mouse/cursor response on a fast machine?
I have a system that has always displayed poor cursor redraw performance with certain adobe applications. All rendering and other effects are fast, but basic mouse selections and button knobs are extremely unresponsive. I have searched and search
-
Time machine won't connect to my shared external hard drive connected to my airport utility
I connected my hard drive directly to my iMac and have backed up my system. Ive since connected the external hard drive to my airport utility. I can save documents to my hard drive wirelessly however when I've tried to back it up again I'm unable to
-
From Not opening in Browser fully
Hello Sir I have one problem that when I run my form in 9i it just show form in a fix space not in whole window (IE browser). It shows scroll bar and I have to move scroll bar to see column in form . While I have sufficient space in browser. In short
-
IOS7 screen rotation :in app smooth - homescreen not so
I just noticed that the screen rotation isn't as smooth as before on the homescreen since IOS 7 . But within an app the rotation is still smooth. iPad3 here.
-
There is a problem with the auto-extractor. Manually extract the files from the downloaded file using Winzip and extract to a new folder. Then run Setup.exe from that folder. Also, make sure that your Temp folders have been cleared out. The latest ve