Bonjourpssetup.exe has expired certificate - can I run it safely?

The file downloaded from apple.com named BonjourPSSetup.exe has a certificate which expired on 6/26/2011. How can Apple be so uprofessional as to post an executable file for the public to download which has an expired code-signing certificate? Are we users supposed to close our eyes and ignore the expired security certificate? If Apple wants to offer Bonjour, they should provide programs which have up to date security certificates.

I just went ahead and did it (shift click on update - and choose restore file downloaded from dev page)
And it worked fine it seems.
No need to restore from backup
Thanks for the help
Steven

Similar Messages

The context has expired and can no longer be used

I am running across a repeatable error when accessing a specific Site Collection. EVERY TIME the SC is loaded we receive the error 'The context has expired and can no longer be used'.
I have already validated the SharePoint servers' time zones are all the same and match the web application(s), as well as set the 'Web
page Security validation' to "Off".
What else could I be missing? Could this have anything to do with Distributed Cache?
- Rick

Hi,
We just began to have the same error. The servers are also correctly set for the timezone (UTC) as well as the Web Applications.
The error happens for every site collections, there isn't a specific site where I'm able to reproduce the issue.
This is the ULS :
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:06.00 w3wp.exe (0x1524) 0x0780 SharePoint Foundation Runtime tkau Unexpected System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) 01ff949c-98cc-d0fb-9795-c691c2852f54

SharePoint Navigation Error:The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Hi,
I take a exeption on the SharePoint 2013 left navigation.
Exeption: "The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)"
I searched this exeption keyword on the internet and I find usualy 3 results
1)check datetime servers --> I checked datetime for all SP Severs ,DB server and AD server ..there is no problem
2)Disabled the WebPageSecurity Validation on CA>General Settings-->I tired and problem not solved
3) Reset IIS --> if I restart IIS problem solved but after 2-3 hours or anytime error comes again..
ULS Log:
PortalSiteMapProvider was unable to fetch children for node
at URL: /MySite/MySubSite, message: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317), stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout,
Boolean bAsAnonymous)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings.GetSiteNavigationSettings(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedHiddenTypes)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetChildNodes(PortalSiteMapNode node, NodeTypes includedHiddenTypes)
Plaase Help.

Hi Veli,
Please check the security token timeout value and it is set to 1440 as expected by default. You can check via running the command:
stsadm -o getproperty -pn token-timeout
Then check the OOB recycle times of the probkematic web application pool, and add daily recycle times for the problematic web application pool. You can do as the article:
http://technet.microsoft.com/en-us/library/cc754494(v=WS.10).aspx
Best Regards,
Wendy
Wendy Li
TechNet Community Support

The context has expired and can no longer be used errors making farm unusable

There are a couple of other posts on this forum about the message "The context has expired and can no longer be used" but they all suggest something related to time and time zone differences. This is not the case in my farm and I have disabled
the security checking of requests on my web applications. Hopefully someone at Microsoft is very aware of this and is working to resolve it because my farm and many others are unusable like this.
I have dug through all of the ULS errors when it happens and there is nothing useful. It barely even registers as a message although, I have not turned on verbose logging, which I am about to try. I have SP 1 installed. Just to be clear, this is happening
on SharePoint 2013 Enterprise.
I have been fighting this for a month. I can add a few things about the farm I am trying to fix:
1. It was a WSS 3.0 farm that when through a 2007-2010-2013 migration in short order.
2. I believe it is under-powered on the hardware side. All VMs on a host shared with 40 other VMs, some fairly busy. Here's the virtual farm breakdown:
-1 WFE with 12GB RAM and 2 cores
-3 app servers with similar resources
-No paging file on C: on any VM. This is a decision by sysadmin. Paging on D: is system managed. Probably irrelevant.
3. Rapidly clicking from link to link seems to bring on the failure much sooner.
Any suggestions even about how to troubleshoot this would be appreciated.

Ultimately, I think it is a time sync issue across the farm. We still have request management off on all boxes because I cannot get the admins to resolve this issue but, in my lab environment I ran into a similar thing.
I may turn RM back on later to see if it comes back but here's what I think happens: In production we have 2 ESXi hosts and our SP environment is all AD (of course). The clocks are all out of sync, sometimes beyond 5 minutes. (The time sync for AD is something
I believe a lot of admins don't understand when running virtual.)
If you allow ESXi to try to sync the time for all guests you run into problems. Maybe they are more pronounced with SharePoint. Anyway, VMware and AD start fighting over the time (check your event logs) and, for us, the clocks across the domain get out of
sync beyond the 5 minute allowable window.
I recommend disabling time sync from host to guest and do what MS recommends: make your domain controller the master time server and configure it to get its time from a reliable source (which can be a single hardware host over NTP). Make other domain controllers
sync from the PDC. The other windows machines will all sync to the domain when they log in. This will prevent SharePoint from issuing tokens from one machine that are out of sync time-wise with the other machines and thus throwing the "Context has expired
and can no longer be used" errors.
Note that disabling host to guest time sync is not as simple as just clearing / un-checking the box in the VSphere client. That doesn't do it. You will need to Google for the 6 or so custom properties you must add to each guest to prevent VMWare from re-synchronizing
after certain hardware events.

The Context has expired and can no longer be used error

Hello All,
I am getting ‘The context has expired and can no longer be used.’ error.
The last thing that was modified on the farm was Distributed Cache Service.
We stopped it on the application server and only have it run on the two WFE’s servers.
Also the cache size was changed to 2048MB.
Is it possible that this change is causing the error?
We don’t have ‘Default Time Zone’ selected for the web application.
But we never saw this error till now.
Any suggestions?
Thank you,
Zabcia

Hi Zabcia,
Thanks for posting this issue,
following could be the reason of raising this issue
1. Security context of your session might be expired
2. Somebody/you might have change the data time of your server.
you can follow below mentioned steps to fix this issue
Just change/update the Date/Time in the SharePoint server
Increase the Security context in SharePoint central admin. This can be done by following the below steps:
Go to central admin
Go to "Application management section" Go to "Web Application General Settings"
Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

HT1918 my account in app store has expired how can i update my account ??

my account in app store has expired how can i update my account ??

Changing Account Information
http://support.apple.com/kb/HT1918

I got a error(The Content has expired and can no longer be used)

Hi,
I built a SharePoint 2013 Farm.
Infrastructure composition is:
・WebFrontEnd Server * 2(Web#1,Web#2)
・Application Server * 1
・SQL Server * 1
・OfficeWebApps Server * 1
・etc(DPM,AD,DocAve)
Site composition is:
・Community Site(Customize Site)
・Enterprise Search Center
After that, I added a WebWebFrontEnd Server(Web#3) to the SharePoint Farm.
So, I had a trouble.
The Enterprise Search Center had not been able to displayed in Web#1 and Web#2.
But, Web#3 is displayed Enterprise Search Center.
When The Enterprise Search Center had not been able to displayed, I get a error message.(The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317))
Does Anyone have the same trouble?
Thanks,
Tomohiro

HI tomohiro,the issue could be of many reasons like the Time not set correctly,App pool.Please check the below link that gives more information on the resolution.
http://expertsharepoint.blogspot.de/2014/10/the-context-has-expired-and-can-no.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317)

I have followed the instructions on this blog. http://blog.cloudshare.com/2012/10/22/how-to-fix-sharepoint-2013-web-application-error-the-context-has-expired-and-can-no-longer-be-used/ and
it fixes the problem for a short time. I have to keep doing IISResets to get my farm backup.
Please Help.

Have you trid Ajay Khanna's suggestion from the comments field?
From Central Admin- Select the web application and Select --> Web Application General Settings --> Navigate to 'Web page Security validation', change or disable the timeout field.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

We have a problem with our wiki site collection. Once a day (and sometimes more), we get the following error message :
The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
This message is displayed to everyone, and will stay there for an hour or so before the collection is back to life.
Doing an iisreset would get the site working but that will last for a day at the most.
This is what we checked and tried so far :
1. Our time zones are set and are correct.
2. Changing the timeout or disabling the web page security validation (followed by an iisreset) didn't work.
3. All server use the same NTP server for time sync (and they are indeed in sync).
4. It is happening only on the wiki collection, not the other collections.
5. We are unable to reproduce the behavior on the staging servers.
Some particularities :
1. Regional settings are set to French (Canada)
2. We have 500+ wiki pages in the site collection
3. We require page check-out / check-in for editing. Tried without, same problem.
Any ideas as to what should we try next ?
Regards,
homerggg

Hi,
I don't think we have changed them from the default, a quick look shows ours are set to:
Token-timeout = 24hrs
FormsTokenLifetime = 10hrs
WindowsTokenLifetime = 10hrs
LogonTokenCacheExpirationWindow = 10m
Rob

I have an aluminium Macbook Pro 15" from around 2009 currently running 10.5.8. Apparently I need to be on 10.7.2 to get into iCloud. System Profiler says my machine is Core Duo, but also says it has 2 cores - can I run 10.7.2 on this machine?

I have an aluminium Macbook Pro 15" from around 2009 currently running 10.5.8. Apparently I need to be on 10.7.2 to get into iCloud. And I can only run 10.7.2 on a Core 2 Duo machine or above? System Profiler says my machine is Core Duo, but also says it has 2 cores - can I run 10.7.2 on this machine? Any feedback welcome.

Read Lion's general requirements.

I have a license of the PSE 11, recently expired, to find out what was going on I have PSE 11 uninstalled. Reinstall does not work because the license has expired. Can I purchase the upgrade version of PSE 12 now or should I buy a full program?

I have a license of the PARTY 11, recently expired, to find out what was going on I have PSE 11 uninstalled. Reinstall does not work because the license has expired. Can I purchase the upgrade version of PSE 12 now or should I buy a full program?

Ok thank you, I better can wait then.
Greetings, Evert Annen
Op 8 sep. 2014 19:45 schreef "Peru Bob" <[email protected]>:
I have a license of the PSE 11, recently expired, to find out what
was going on I have PSE 11 uninstalled. Reinstall does not work because the
license has expired. Can I purchase the upgrade version of PSE 12 now or
should I buy a full program? created by Peru Bob
<https://forums.adobe.com/people/Peru+Bob> in Photoshop Elements - View
the full discussion <https://forums.adobe.com/message/6711348#6711348>

Message: Your Server's SSL certificate has expired. - Can no more login

Hi,
Since yesterday I can no more login into beehiveOnline via OBEE. Every time I try it the extension goes offline and tells me in a window that "Your Server's SSL certificate has expired.". If I try to relogin it takes some seconds but the window and message comes up again and again.
It was working perfectly during the previous weeks, no issues at all. What do I have to do to get it solved?
Thanks
Volker

Hello,
I've set up OBEE for BeehiveOnLine usage today, without any issue (Monday 28 of June)
May you retry please?
Yesterday - Sunday - the system might be under maintenance.
Thanks
Fred

Synch request has been cancelled. can't run it again.

The error message is:
DEFAULT synch in Progress.. Cancelling new synch request.
Once I try to fire "Run synch", I always get this Msg.
Thanks in advance.

Hi Ryan,
when the sync starts the Sync Tool creates a 0 Byte file called "Synch.lock" in whatever folder you installed the synch tool.
Locate and delete this filem and you will be able to sync again.

I have the basic version of Lightroom and found that my mobile app has expired. Can I just purchase the mobile app? If so how much is it?

how I'd I get just the moblie app?

Lightroom Mobile is a companion to the desktop version - it's not intended as a stand-alone product.

Certificate on phone has expired

When i try to download nfs run social from nokia store its showing "Certificate on phone has expired"
what can i do
please help me

Do you mean the app NFS The Run Social?
It is not available in my country to double check. Where do you live? Then, I try to find a proxy to look at it. Anyway, please, make sure the date especially the year is correctly set on your phone. If that does not help, go back by one year, try again, two years, try again, three ‥. If that does not help, please, go to Nokia 311 » Menu » Settings » Security » Authority Certificates: Are there more than four certificates?

Bonjourpssetup.exe has expired certificate - can I run it safely?

Similar Messages

Maybe you are looking for