HT1331 The menu on my airport utility does not match that which is described in in this article

I am trying to mount and share a 2TB USB WD drive on an airport extreme. This will be used for time machine backups and large video file storage.
I have successfully (at least the system said it was successful) written and read the graphics files and completed a full time machine backup on the drive.
There was a Time Machine backup on this drive, but Time machine didn't seem to want to use it, so I created another. The one I created is approximately the size of my MAC hard drive data, is called "bfmj9.sparcebundle" and is dated when the full backup completed. There is another folder in the directory called "backups.backupdb" which comprises many files which look like dates. It was last updated before I started to the backup yesterday.
So I called support and was given some instruction and Apple documents which seemed to have a different menu structure than what my AirPort Extreme shows. In particular, one says to:
Manually mounting hard disks using the AirPort Disk menu bar item
Click the AirPort Disk menu bar icon () and select the Base Station with desired USB hard drive.
Select the desired hard disk(s) (AirPort Disk).
Enter the username and password required to access the AirPort Disk(s).
When I click on the menu item, I do not get the list of hard disks.
Perhaps I have set the disk up incorrectly. The strange part is that both the new time machine backup and my other files are behaving properly.
Thanks for any help you can give.
Barry

Apple updated the airport utility but have not updated the documentation for some time.. really slack considering it is significantly different.
The new utility is a poor substitute for the original and perhaps by not publishing new manuals they can hide their shame at how much functionality they removed.
It is possible to load a real utility even into mountain lion.. I strongly recommend you do so.
Download the real utility.
http://support.apple.com/kb/DL1482
Click to open the DMG so you can see the pkg file.. do not proceed further. It cannot install onto ML.
Download unpkg, install and run it.
http://www.timdoug.com/unpkg/
Drag the airport utility pkg onto unpkg.. and presto.. it will be unpacked to a new directory on your desktop.. AirPortUtility56 .. now drill down to Applications Utilities. And there is your new shiny tool.. drag it to your existing utilities folder.. or just start from there.
Not hard and unpkg is free.
You cannot remove 6.1 toyland version so just ignore it.. as it richly deserves. Do not attempt to run both.
Just remember when you want the airport utility start the real one. 5.6

Similar Messages

Reader version listed in GUI does not match that of executable file (again)

I posted regarding this issue before (http://forums.adobe.com/message/4817948), but was never able to find an answer.
Presently I am deploying Adobe Reader 10.1.5 via the MSI installer and group policy. The issue is that a user shut down her Windows 7 computer midway though the MSI installation interrupting (i.e. screwing up) the installation process. I had to delete a few registry entries and reboot the user's PC in order to re-initiate the Reader installation (something I've done in the past).
To verify that Reader was installed sucessfully, I browse to the Reader executable (AcroRd32.exe) in Program Files, double click the executable, select About Adobe from the Help menu, check the version number in the information box and see that the version number is 10.1.4 (i.e. the old version that I am upgrading from). However, when I browse to the Reader executable (AcroRd32.exe) in Program Files and and open the file properties, I see that the version is 10.1.5 (i.e. the new version that I am upgrading to).
So the Reader version listed in GUI does not match that shown in the executable property box.
This is the second time that this has happened with a Windows 7 PC. I've never experienced this sort of thing with a Windows XP PC.
Why is the version number different in the GUI? Where is the version number read in from for the GUI? The registry? Can anybody shed some light on this situation?

Let me clarify that the tool posted on http://labs.adobe.com/downloads/acrobatcleaner.html is not the uninstaller for Reader. Instead it is a cleaner tool used for any botched up installation as mentioned above. This utility should only be used in rare circumstances. Instead reader has its own uninstaller which can be used through ARP (Add Remove Programs) in Windows or you can also use the command line "msiexec /x AcroRead.msi" to uninstall Reader.
Thanks,
Vinod

Reader version listed in GUI does not match that of executable file

I have an interesting situation...
I have Adobe Reader X installed on a Windows 7 desktop. When I go to the Reader installation files right click on the executable (AcroRd32.exe) and open properties, I see that the version is 10.1.4.38 and that the update date is July 28th 2012 (Which is consistent with the Reader X 10.1.4 release date). However, when I double click the same executable file and open About Adobe from the Help menu, the information box that appears states that the reader version is 10.1.3.
So the Reader version listed in GUI does not match that of executable file's properties. Very, very strange.
I am fairly sure that the version stated in the property box is correct, but am not 100% certain. So where is the version number read in from for the GUI? The registry? Can anybody shed some light on this situation?

I don't know why you are seeing that, my Adobe Reader 10.1.4 shows this

HT1998 My iPAD can use the internet through my airport extreme, but the airport utility does not see it so I can't create a guest password. What am I doing wrong?

My iPAD can use the internet through my Airport Extreme, but the Airport Utility does not see the device so I can't set a guest password.

If your Mac is using the Lion operating system with recent updates, it will be necessary to download and install AirPort Utility 5.6 for Mac OS X Lion
Open Macintosh HD > Applications > Utilities > AirPort Utility 5.6
Select the AirPort Extreme and click Manual Setup
Click the Wireless tab just below the row of icons
Click the Wireless Network Options button
Remove the check mark next to Create a closed network
Click Done, then click Update to save the new settings and allow 25-30 seconds for the AirPort Extreme to restart

The airport utility does not find my Airport Extreme. I tried to reset the base, but I can`t make it. What can i do?

The airport utility does not find my Airport Extreme. I tried to reset the base, but I can`t make it. What can i do?

Please perform a Factory Default Reset exactly as follows:
Pull the power plug from the back of the AirPort Extreme (AEBS)
Wait a minute
Hold in the reset button first and continue to hold it in for at least 7-8 more seconds while you simultaneously plug the power back in to the AEBS
Release the reset button after the 7-8 second hold period
Allow 30-45 seconds for the AEBS to restart
Temporarily, connect a spare Ethernet cable from your Mac to one of the LAN <-> ports on the AEBS
Open AirPort Utility to see if can now see the AEBS

My airport utility does not find my airport express device

My airport utility does not find my airport express device

In order for the AirPort Utility on your iOS device to find the Express, both need to be connected to the same Wi-Fi network. By default, the Express will broadcast an unsecured wireless network with a network name of something like: Apple Network NNNNNN. Can you iOS device find this network?

Windows 7 airport utility does not recognize my airport extreme

My iphone connects to my airport extreme and the airport utility sees it. So does my ipad and my friends laptop.
When I use wifi or wired connection (to lan port) from Windows 7 laptop to my airport extreme. The airport utility does not "see the extreme.
I've uninstalled/reinstalled the following:
- bonjour
- airport utility
- itunes.
I've wasted 3 hours on this.
Any help will be greatly appreciated.....

UPDATE
* I located the IP address and admin password of the airport extreme and was able to log into to the (File / configure other) airport extreme.
I believe it's a W7 bonjour issue.
As you can see in my attachments, Bonjour is installed however msconfig running services show it as stopped. I can't get it to start.
** How can I force bonjour to start? **
Here are my replies to your recommended steps:
What version extreme are you talking about? Actual model A1xxx from the base is a big help.
- I forgot to check this
Step 1.. Ping.. Ping is your most important tool to find things on a network.
Open a command window and type ping 10.0.1.1 (or whatever is the current IP of the extreme).
- Yes, I can ping it.
Please turn off all firewalls.
- Yes, firewall is off
Make sure the win7 is not in homegroup.
- done.
Make sure win7 is set to home.. not work or public for location of the network.
- done.
Step 2. .. This assumes you now have ping response.
In whatever airport utility you like, reset the extreme to use all SMB names.
- WHERE do I make these changes?

Airport utility does not support base station? Help!

I cannot get base station light to turn green. Blinking amber. I upgraded to a new Verizon modem and since then the base station does not work. What can I do?

Make sure the new Verizon Modem is not also a WiFi Router, if it is then that may be your issue. If it is indeed just a Modem then your Ethernet Connection should work and your base station should be working. You said "Airport Utility does not support base station". Don't know what you meant by that. Do you have an Airport Extreme, Airport Express or a Airport TC as a Base Station? If yes, you should be able to set up your Network via Airport Utility. If the Verizon Modem is only a Modem then unplug the power from your Airport Base Station, then unplug the Power from your Verizon Modem for at least 1-minute. Plug the Modem back in and give it a moment or so, then make sure you do have an Ethernet cable going from your Verizon provided Modem to your WAN port on your Airport Base Station. Now power up your Airport Base Station and go to your Airport Utility. Find the Base Station and click on Edit... Make sure your Network Name is correct, your Password is Correct, your Security method is correct (example: WPA2 Personal). If all correct see if your blinking Amber light is now Solid Green.

Since I've upgraded to Maverick the airpot utility does not recognise that there is a time capsule on the wireless network. I can see the TC using the air port utility on my iPhone5 and on my iPad. What am I doing wrong on my macbook?

Since I've upgraded to Maverick on my Macbook Pro the airpot utility does not recognise that there is a time capsule on the wireless network. I can see the TC using the air port utility on my iPhone5 and on my iPad. What am I doing wrong on my macbook?

I have over 250G backed up and I really don't want to reset everything and start again.
Not sure what you mean here.
A reset will not affect any of the data on the Time Capsule hard drive. You would have to perform a completely separate and very deliberate Erase Disk operation for that to occur.
I'm not recommending that you perform a default reset, but it is an option if there is really nothing else to try.
I don't know if what you are seeing is a Mavericks issue or not, since I refuse to use any new software until at least the first major update with fixes comes along.
Another user may be able to offer more input on Mavericks.

The name on the security certificate is invalid or does not match the name of the site

Hi Guys,
Every time when we login to SAP Business One, we are getting two identical security Alerts, that we needs to click "Yes" twice.
Text of error: “The name on the security certificate is invalid or does not match the name of the site”
We tried to install certificate, but it is not solved this certificate issue and the alert still pops up on login.
I guess, something wrong with dashboard settings, but don't really know what exact and how to fix it.
Thanks,
Sergey

Hi,
Please check SAP note:
1810486 - Dashboard Certificate Sercurity Alert appears on every
logon to Business One
Thanks & Regards,
Nagarajan

Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040

Please assist I am on a Windows 7 64 bit machine I have VS 2010 and have been fighting with this new program that I was brought on to help with - Issue is that I am unable to get rid of this issue. There is so many solutions but none have worked. If someone can give me some help with what has worked for you.
The error is Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
This is with CR installed on 64 bit.
Thank you very much for any assistance with this problem,
Kris

Hi Vittorio
Please enter the search string 'log4net crystal net' into the search box in the top right corner. When the results come up, click on the Support Notes link. That will filter for the KBAs that you want to have a look at.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
===========================================================
This is a SQL Server 2012 Developer Edition of SSRS.
I am getting this error when navigating to http://servername/Reports. The reports site was working fine, until I installed a SQL 2014 Developer instance (including SSRS) on the same server.
I can still get to the http://servername/ReportServer site.
Neither of these are using Sharepoint.
Any help resolving this issue would be greatly appreciated.
Below is the stack trace.
===========================================================
[FileLoadException: Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)] System.Reflection.Assembly._nLoad(AssemblyName
fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity,
StackCrawlMark& stackMark, Boolean forIntrospection) +416 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +166 System.Reflection.Assembly.Load(String
assemblyString) +35 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +190 [ConfigurationErrorsException: Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel'
or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +1149
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +323 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +116 System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +36 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection
compConfig) +212 System.Web.Compilation.WebDirectoryBatchCompiler..ctor(VirtualDirectory vdir) +174 System.Web.Compilation.BuildManager.BatchCompileWebDirectoryInternal(VirtualDirectory vdir, Boolean ignoreErrors) +57 System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath
virtualPath) +295 System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +482 System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext
context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +108 System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean
noAssert) +171 System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +52 System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext
context, String requestType, VirtualPath virtualPath, String physicalPath) +53 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +519 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+176 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +274
===========================================================

Hi Glen，
"The located assembly's manifest definition does not match the assembly reference." is generally caused by the loaded assembly's version is different than the expected version application refers to.
In this case, it should be caused by:
While starting Report Manager, the backend process ReportingServiceService need to load assemblies it refers to
ReportingServiceService reads the compilation/assemblies element from web.config(under Report Manager virtual patch)
If the compilation/assemblies is not existing, ReportingServiceService loads all assemblies from Bin folder. It can be verified from call stack System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory(). ReportingServiceService
uses System.Reflection.Assembly.Load with the assemblies' name only to load assemblies.
The Assembly.Load tries to load from the specify assembly by name from GAC at first. If it is found from GAC, it won't be loaded from Bin folder any more.
Since Reporting Service SharePoint Integration mode is installed, a same assembly of 'Microsoft.ReportingServices.SharePoint.ObjectModel' with different version might be installed to the GAC. That causes the error "The located assembly's manifest definition
does not match the assembly reference."
For more information about the error message and the loading process, please see:
http://blogs.msdn.com/b/junfeng/archive/2004/03/25/95826.aspx
https://msdn.microsoft.com/en-us/library/yx7xezcf(v=vs.100).aspx
Thanks,
Jinchun Chen

The name on the security certificate is invalid or does not match the name of the site" : IE

Hi All,
All clients are getting “the name on the security certificate is invalid or does not match the name of the
site” when its reboot and try to access website.
I don’t have idea about certificate authority. Can anyone help on how I start troubleshooting this.
Is there any group policy setting which resolve this issue.
Please suggest what parameter I have to check.

> All clients are getting “the name on the security certificate is invalid
> or does not match the name of the site” when its reboot and try to access website.
"View Certificate" should tell you.
Greetings/Grüße,
Martin
Mal ein
gutes Buch über GPOs lesen?
Good or bad GPOs? - my blog…
And if IT bothers me -
coke bottle design refreshment (-:

Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of. I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
clients get prompted for a security warning. I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine. My Outlook 2013 client doesn't prompt me with the message but I have other users who are
still getting the "The name of the security certificate is invalid or does not match the name of the site" error. The domain on the cert error show up as server.mydomain.local. I've gone through all the virtual directories and pointed
all of my internal and external URL's to https://mail.mydomain.com. This made one of the two warnings go away but not the second. I've dug around on google and gone through everything I could find here and as far as I can tell my internal
and external url's are configured properly and I can't figure out where this error is originating from. Any ideas on where I should look outside of the virtual directories?
I'm including a good link I found that contains all of the virtual directories I updated. I've checked them through both CLI and GUI and everything looks good.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

Hi,
When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
Regards,
Winnie Liang
TechNet Community Support

The name of the security certificate is invalid or does not match the name of the site error?

I am looking for some help folks. We are in a Outlook 2007/Exchange2010/Windows2008R2 environment.
When users open Outlook off the network, and occasionally on the network, they get the error
The name of the security certificate is invalid or does not match the name of the site error
The CAS hostname is HRECAS.XXX.ORG. The URL that is listed on the SSL certificate (issued by VeriSign) is WEB.XXX.ORG. WEB.XXX.ORG is what users use to get to OWA and such.
When I use testexchangeconnectivity.com, under certificate name validation I see an error that reads:
Host name autodiscover.xxx.org doesn't match any name found on the server certificate CN=web.xxx.org.
Does this mean somehow we have to add autodiscover.xxx.org on the certificate?
I tried to add AutoDiscoverExternalUri using
http://support.microsoft.com/?kbid=940726 &
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/2d0c0f5f-e4ec-4f33-a37d-b94fd7a2319f on the CAS server.
Set-ClientAccessServer -identity HRECAS -AutodiscoverServiceExternalUri
https://autodiscover.xxx.org/Autodiscover/Autodiscover.xml
I get an error that says
"a positional parameter cannot be found that accepts argument '-AutoDiscoverExternalUri'.
Can someone point to me what I am doing wrong with the command and whether I should be concerning myself with adding that line? By the way the
InternalUrl information is already configured on the system. Also should I edit the certificate to add autodiscover.xxx.org?
Thank in advance for your support.
TD
TD

Hi Tapera,
Thanks for the question.
SRV record is a good idea. You can set the SRV to
https://web.abc.com/autodiscover/autodiscover.xml but you must make sure the
url can be resolved from External clients.
In addition, there is still a issue. It is hard coded that Outlook will find the autodiscover by the orders below:
1. Access autodiscover via SCP in AD.
https://web.abc.com/autodiscover/autodiscover.xml
2. If SCP access fails, it will try:
https://abc.com/autodiscover/autodiscover.xml
3. Then
https://autodiscover.abc.com/autodiscover/autodiscover.xml
4. Local XML file
5. SRV record
As you can see, Outlook will try SRV record at last. Therefore, it will still try to access
https://autodiscover.abc.com/autodiscover/autodiscover.xml each time you run Outlook. Then the certificate warning will still persists.
I have a workaround solution. You can do a local policy to disable the autodiscover to access the
https://autodiscover.abc.ocom/autodiscover/autodiscover.xml by:
1.
On the Outlook client machine, open regedit and add the following key:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Autodiscover
         "ExcludeHttpsAutodiscoverDomain"
         "ExcludeHttpsRootDomain"
2.
Then set the value to “1” on the above two keys.
Thanks,
Simon

HT1331 The menu on my airport utility does not match that which is described in in this article

Similar Messages

Maybe you are looking for