010SM: ...does not support the initial proposed set of capabilities...

          While I was testing a data extraction servlet that takes a sql statement from an HTML form document, I got the following errors in the jdbc log. I don't understand what the jdbc log entry is telling me.
          Here's my configuration:
          jdbc 20 connection with jConnect 5.2 driver
          Weblogic Server 5.1
          Perhaps you can help me.
          regards,
          Jackle
          SQLWarning: reason(010SM: This database does not support the initial proposed set of capabilities, retrying.) SQLState(010SM)
          SQLWarning: reason(010SM: This database does not support the initial proposed set of capabilities, retrying.) SQLstate(010SM) vendor code(0)
          java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
          at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:426)
          at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:2794)
          at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java, Compiled Code)
          at com.sybase.jdbc2.tds.Tds.logout(Tds.java, Compiled Code)
          at com.sybase.jdbc2.tds.Tds.login(Tds.java:359)
          at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java, Compiled Code)
          at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:190)
          at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:169)
          at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:122)
          at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:175)
          at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:149)
          at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:109)
          at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java, Compiled Code)
          at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java, Compiled Code)
          at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
          at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java, Compiled Code)
          at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
          at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
          at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled Code)
          at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
          SQLException: SQLState(JZ006)
          registerDriver: driver[className=weblogic.jdbc20.jts.Driver,weblogic.jdbc20.jts.Driver@78bf9ff2]
          registerDriver: driver[className=weblogic.jdbc20.pool.Driver,weblogic.jdbc20.pool.Driver@64b39ff2]

Reduce the complexity of the SQL statement until you do not receive the
          error. Add back the functionality until it breaks. At that point, you can
          see what feature that the driver/database does not support.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Jackle" <[email protected]> wrote in message
          news:[email protected]...
          >
          >
          > While I was testing a data extraction servlet that takes a sql statement
          from an HTML form document, I got the following errors in the jdbc log. I
          don't understand what the jdbc log entry is telling me.
          >
          > Here's my configuration:
          >
          > jdbc 20 connection with jConnect 5.2 driver
          > Weblogic Server 5.1
          >
          >
          > Perhaps you can help me.
          >
          > regards,
          >
          > Jackle
          >
          >
          > SQLWarning: reason(010SM: This database does not support the initial
          proposed set of capabilities, retrying.) SQLState(010SM)
          > SQLWarning: reason(010SM: This database does not support the initial
          proposed set of capabilities, retrying.) SQLstate(010SM) vendor code(0)
          > java.sql.SQLException: JZ006: Caught IOException: java.io.IOException:
          JZ0EM: End of data.
          > at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:426)
          > at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:2794)
          > at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java, Compiled Code)
          > at com.sybase.jdbc2.tds.Tds.logout(Tds.java, Compiled Code)
          > at com.sybase.jdbc2.tds.Tds.login(Tds.java:359)
          > at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java,
          Compiled Code)
          > at
          com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:190)
          > at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:169)
          > at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:122)
          > at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:175)
          > at
          weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
          EnvFactory.java:149)
          > at
          weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
          EnvFactory.java:109)
          > at
          weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
          ava, Compiled Code)
          > at
          weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java,
          Compiled Code)
          > at
          weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330
          > at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,
          Compiled Code)
          > at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
          > at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
          > at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled
          Code)
          > at
          weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
          > SQLException: SQLState(JZ006)
          > registerDriver:
          driver[className=weblogic.jdbc20.jts.Driver,weblogic.jdbc20.jts.Driver@78bf9
          ff2]
          > registerDriver:
          driver[className=weblogic.jdbc20.pool.Driver,weblogic.jdbc20.pool.Driver@64b
          39ff2]
          >
          >

Similar Messages

OATS CPU does not support the SSE2 instruction set required to run JRockit

Hello,
I am trying to get the OATS agents to work on some injector machines, however, when I try to start them I get the following error:
"[ERROR] Your CPU does not support the SSE2 instruction set required to run JRockit.
Could not create the Java Virtual Machine."
Is there a way to configure OATs to use the Sun JDK instead? I have the Sun JDK in my path and JAVA_HOME set accordingly, however that doesn't seem to make a difference. Alternatively, is there a workaround to this problem?
Thanks,
Michael.

Hi Tab,
In this case, SQL Server Analysis Services doesn’t support Distributed Transactions by design. Here is a similar thread about this issue for your reference, please see:
http://social.technet.microsoft.com/Forums/en-US/8b07be45-01b6-49d4-b773-9f441c0e44c9/olaplinked-server-error-msolap-for-linked-server-olaplinked-server-does-not-support-the?forum=sqlanalysisservices
One workaround is that use SQLCMD to execute the EXEC AT command and saved the results to a file, then import using SSIS.
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Cat0-3750 upgrade. Error: system number 1 does not support the same feature

I am trying to upgrade or rather downgrade from ipadvservices (inadvertently upgraded to) to ipservices on a stack of Cat-3750s, but I get the following error message:
Ios Image File Size: 0x00877A00
Total Image File Size: 0x00B04200
Minimum Dram required: 0x08000000
Image Suffix: ipservicesk9-122-37.SE1
Image Directory: c3750-ipservicesk9-mz.122-37.SE1
Image Name: c3750-ipservicesk9-mz.122-37.SE1.bin
Image Feature: IP|LAYER_3|PLUS|SSH|3DES|MIN_DRAM_MEG=128
Error: The image in the archive which would be used to upgrade
Error: system number 1 does not support the same feature set.
Any ideas?
Chris

I was having the same issue even with entering the following:
archive download-sw /overwrite /allow-feature-upgrade tftp://172.18.108.26/c3kx-sm10g-tar.150-2.SE7.tar
I noticed the image which was running on the switch was correct without the ".bin" at the end:
3560#sh ver | i image
System image file is "flash:c3560e-universalk9-mz.150-2.SE7"
I uploaded a fresh IOS image from CCO and made sure the image name had ".bin" at the end. Seems trivial except the error is produced through a sanity check. See below (please excuse the extra unplugging in the output):
3560#sh ver | i image
System image file is "flash:c3560e-universalk9-mz.150-2.SE7.bin"
3560#$de tftp://172.18.108.26/c3kx-sm10g-tar.150-2.SE7.tar
Loading c3kx-sm10g-tar.150-2.SE7.tar from 172.18.108.26 (via Vlan1): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!                             !!!!!!!!!
Mar 30 01:33:35.480: %USBFLASH-5-CHANGE: usbflash0 has been removed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Mar 30 01:34:15.636: %PLATFORM_ENV-1-FRU_PS_ACCESS: FRU Power Supply is not responding!!!!!!!!!!!
[OK - 24893440 bytes]
Loading c3kx-sm10g-tar.150-2.SE7.tar from 172.18.108.26 (via Vlan1): !!!
Mar 30 01:34:35.593: %PLATFORM_ENV-6-FRU_PS_OIR: FRU Power Supply 2 removed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!                             !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
examining image...
extracting info (100 bytes)
extracting c3kx-sm10g-mz.150-2.SE7/info (499 bytes)
extracting info (100 bytes)
System Type:             0x00010002
Ios Image File Size:   0x017BDA00
Total Image File Size: 0x017BDA00
Minimum Dram required: 0x08000000
Image Suffix:          sm10g-150-2.SE7
Image Directory:       c3kx-sm10g-mz.150-2.SE7
Image Name:            c3kx-sm10g-mz.150-2.SE7.bin
Image Feature:         IP|LAYER_3|MIN_DRAM_MEG=128
FRU Module Version:    03.00.78
Updating FRU Module on switch 1...
Updating FRU FPGA image...
FPGA image update complete.
All software images installed.
Worked for me, hope this helps.

Just changed my router to Airport. Mac Lap top and IPad works OK except my VAIO desk computer. It says that airport does not support the setting of the computer. Check the security setting. Whar

Just changed my router to airport extreme
My MacBook pro and iPad work fine but my VAIO wireless desk computer is not working.
It says
, the router does not support the network .check security setting.
Which of the security setting will I change?
Thanks for your help.

John, thanks for the email so quickly.
I too hope I haven't tried "everything" either but I am reasonably technical. I had done what you suggested to do before but I did both again.
Ethernet is yellow in the left side bar. In the right pane it's status says Connected but then below it says "Ethernet has a self-assigned IP address and will not be able to connect to the Internet."
I have tried the assist me menu and Network Status has Ethernet Green, Network settings Yellow, ISP Green, and Internet and Server Red and Failed for both. I have turned things off and on, checked cables, deleted all locations and tried restting them up but to no avail. I even disconnected everything and connected the mac directly into the cable modem itself and the thing still will not connect.
Thoughts???

The requested operation could not be performed because OLE DB provider "MSOLAP" for linked server does not support the required transaction interface.

I am getting the following error when attempting to INSERT the results of an "EXEC(@MDXQuery) at SSAS LinkedServer":
The requested operation could not be performed because OLE DB provider "MSOLAP" for linked server does not support the required transaction interface.
Here is code that illustrates what I am doing:
DECLARE @MDX varchar(max);
SET @MDX='
SELECT
[Measures].[Extended Service Count]
} ON COLUMNS,
NON EMPTY [Organization].[By Manufacturer].[Manufacturer]
ON ROWS
FROM (
SELECT
{[Organization].[Org Tree].&[2025],[Organization].[Org Tree].&[2040]} ON 0
FROM [MyCube]
/* Test 1 */
EXECUTE(@MDX) at SSASLinkedServer;
/* Test 2 */
DECLARE @ResultsB TABLE (
Manufacturer varchar(255)
, ExtendedServiceCount float
INSERT INTO @ResultsB (Manufacturer, ExtendedServiceCount) EXECUTE(@MDX) at SSASLinkedServer;
Test 1 succeeds, returning expected results, and Test 2 fails returning the error mentioned above.
Other articles I've found so far don't seem to apply to my case. I am not creating any explicit transactions in my code. When I use OPENQUERY, I am able to do the insert just fine, but not when I use EXEC @MDX at LinkedServer.
Unfortunately in some variations of the query, I run into the 8800 character limit on OPENQUERY, so I need to use this other approach.
Any ideas?
-Tab Alleman

Hi Tab,
In this case, SQL Server Analysis Services doesn’t support Distributed Transactions by design. Here is a similar thread about this issue for your reference, please see:
http://social.technet.microsoft.com/Forums/en-US/8b07be45-01b6-49d4-b773-9f441c0e44c9/olaplinked-server-error-msolap-for-linked-server-olaplinked-server-does-not-support-the?forum=sqlanalysisservices
One workaround is that use SQLCMD to execute the EXEC AT command and saved the results to a file, then import using SSIS.
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Ever since enabling Soft Delete on one of my tables, the logs are flooded with "... does not support the 'deleted' system property"

I enabled Soft Delete on one of my Azure Mobile Services tables, and ever since then, the logs are flooded with tons of warnings that say something like this:
The table 'Section' does not support the 'deleted' system property.
Is there a way to suppress these warnings, or is it advisable to enable soft delete for all of my tables?
As a follow on, is there a way to export the logs so that it's easier to peruse through them and search?
Thanks :)

Hi
You can set your logging level in Azure Admin portal to be Error only, so it only logs errors and warnings will be ignored.
Regards
Aram

Win2012R2 error 364 Content file download failed.Reason: The server does not support the necessary HTTP protocol.

Im running WSUS on Windows 2012 R2. Installed over "Add Roles and Features". Configured, synchronisation works, but can not download any updates.
System
Provider
Name]
Windows Server Update
Services
EventID
364
Qualifiers]
0
Level
2
Task
2
Keywords
0x80000000000000
TimeCreated
SystemTime]
2014-08-27T06:43:36.000000000Z
EventRecordID
390
Channel
Application
Computer
wsus-server.murrcz.local
Security
EventData
Content file download
failed. Reason: The server does not support the necessary HTTP protocol.
Background Intelligent Transfer Service (BITS) requires that the server support
the Range protocol header. Source File:
/msdownload/update/software/crup/2011/03/windows6.1-kb2506014-x64_8c22199a738b51dbfe78262ca21ba98cf8bdeca2.cab
Destination File:
C:\WSUS-updates\WsusContent\A2\8C22199A738B51DBFE78262CA21BA98CF8BDECA2.cab
The online help not works:
Content download has failed. BITS service is not starting or is stopping during downloads.
Open a command window.
Type sc config bits start= auto
Type net stop bits && net start bits
Type net stop wsusservice && net start wsusservice
Start WSUS 3.0: Click Start, click Administrative Tools, then click
Microsoft Windows Server Update Services v3.0.
Click Synchronization Results.
In the Action pane, click Synchronize Now.
Verify
Look for the corresponding error event.
Open a command window.
Type cd <WSUSInstallDir>\Tools
Type wsusutil checkhealth
Type eventvwr
Review the Application log for the most recent events from source Windows Server Update Services and event id 10030.
The KB922330 not aplicable, ExecuteSQL.exe not present.
Please help.
Thanks

.\SQLCMD.EXE -S \\.\pipe\MICROSOFT##WID\tsql\query -d "SUSDB" -Q "update tbConfigurationC set BitDownloadPriorityForegroud=1"
This should be considered a temporary fix. It will saturate your Internet connection during periods of WSUS downloads in this configuration.
The correct and permanent fix should be to resolve the failure of your perimeter device to properly support the HTTP v1.1 protocol specification (which is now some 14 years old).
Either your device is misconfigured, or it needs a firmware update to support the full specification.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Network backup disk does not support the required AFP features

I have a mac mini with two (4T) hard disks each set as target in TimeMachine. Backups have been made on both for some time. This afternoon one of the disks is being rejected as target volume, with the "network backup disk does not support the required AFP features" error.
The sparse image on the disk that is the actual time machine target shows a modification tim of 13:09, time machine reports the last backup on that volume as made on 13:08. It seems the last successful backup was made at that time. The other TimeMachine target volume on the same min reports a last backup at 15:28
So why an error now? What has happend in the last hour, or so, to cause the disk to no longer be suitable? Why only on one virtual disk?
The mac mini runs OS X 10.9.4 (13E28), the disk with the failing backup volume is formatted with Case-Sensitive Journaled HFS+, the still working disk Journaled HFS+.
This may be related: A couple of month ago I lost the complete backup on that disk, when time machine conclude that the contents of the target volume was corrupt. At the time I blamed that at a failed backup when I had accessed the mini over ssh using SLINK when traveling. Maybe that conclusion is wrong and this is part of the same problem.
Any pointers on how to get my second backup disk working again would be much appreciated.
Eduard de Jong

The error message has disappeared!
Earlier this morning the disk has been used as target for a backup by time machine without triggering the error message. A backup 8 hours earlier has also been made to the same sparse image (looking at the folder names).

J2sdk1.4.2_12 does not support the 64 bit data model

Hi guys,
I need support for instalation NW2004R1 for windows x64bit.
in the step "define parameters" I need set JDK Directory, I setting C:\j2sdk1.4.2_12 and when click in botton next, I receive the message " The JDK installed in directory C:\j2sdk1.4.2_12 does not support the 64 bit data model. Choose a different JDK. "
I search documents but not found.
Anybody can help-me ???
thanks
Henrique Mattos.

Hi,
You can get more information related to your issue from
service.sap.com
https://sdlc2e.sun.com/ECom/EComActionServlet;jsessionid=606D9ABC1A37F8F6D7517A9B77ACA38B
Regards
Agasthuri Doss

The network backup disk does not support the required AFP features.

I am trying to set up timeMachine on my new mac book pro over a regular home network on a shared network drive. I have tried everything but I keep getting "The network backup disk does not support the required AFP features." I am on lion with the lateset unpdate (10.7.4). I have even tried creating sparebundles on from tutorial that I have found online, but non of the hacks that I have tried seemed to work. Have anyone figured out a way around this? If so, can you share, it will be greatful. I could just buy the time capsule that apple sells but I already have a 2TB internal HDD in an old pc that's hosting my file server so no need for the time capsule hardware. Let me know if there is a way around this thank.

ookakaa wrote:
1) Apple time capsule
Or USB drive connected to a Time Capsule
2) NAS with the latest firmware
Not just any NAS. It has to support the communications protocols used by Time Machine (some involving security, some about error detection and handling). Some NASs never supported TM; some that worked on Leopard never got updated for Snow Leopard; and some that worked on Snow Leopard still haven't been updated for Lion.
4) Another networked mac (not a pc)
A Mac running Leopard 10.5.6 or later.
Are these the only options?
Those are the only options supported by Apple. Some other destinations may work, to some degree, in some circumstances. Some require "hacks" or other workarounds. Most are somewhat unreliable, and, may stop working at all on the next OSX upgrade.
Side note. I've been seeing some online post of how some people are setting up TM on a networked PC drive by setting up a sparsebundle like this site:
Any thoughts? I have tried some of these examples and it don't seem to work...
Some of those may have worked at one time, in some circumstances (2 are dated before Lion was released, the other is undated).
Wireless backups are tricky enough to a supported destination, with all the security and error detection and handling Apple has been able to employ. If your backups are important to you, don't trust them to a marginal scheme.
And, in any event, don't trust your backups to a single piece of hardware or software. See Time Machine - Frequently Asked Question #27 for an explanation and some suggestions.

AFP error for new hard drive for time machine The network backup disk does not support the required AFP features.

Purchased Seagate network drive, ethernet attached to wireless router, set up went well but attempts at backup with Time Machine failed. "Do I need to erase disk and reformat or is this error message "The network backup disk does not support the required AFP features" indicating some other error?

That means the NAS drive's OS isn't compatible with the version of OSX you're running. See if the maker has an update.
See #C16 in Time Machine - Troubleshooting.

Log onto incoming mail server (POP3): Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance.

Hi All,
This is my first post to ms exchange forum am getting Log onto incoming mail server (POP3): Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator
or Internet service provider (ISP) for additional assistance. in my outlook clients, till last Sunday (12.04.15) my exchange was well & good, Monday morning suddenly the problem started like none of our outlook pop3 clients are able to communicate
with exchange (rest IMAP, SMTP & Exchange accounts are working fine). i have tried with all port no but no luck. please help me to get raid of this one.
Exchange 2013 CU6 with server 2012 Std 64Bit
Thanks,
Murali

Dear All,
I have found the solution for above problem, the problem has occur due to PopProxy inactivity
please find relevant exchange management shell commends below.
1. Get-ServerComponentstate -Identity <yourmailserver.com>
Server Component State
yourmailserver.com ServerWideOffline Active
yourmailserver.com HubTransport Active
yourmailserver.com FrontendTransport Active
yourmailserver.com Monitoring Active
yourmailserver.com RecoveryActionsEnabled Active
yourmailserver.com AutoDiscoverProxy Active
yourmailserver.com ActiveSyncProxy Active
yourmailserver.com EcpProxy Active
yourmailserver.com EwsProxy Active
yourmailserver.com ImapProxy Active
yourmailserver.com OabProxy Active
yourmailserver.com OwaProxy Active
yourmailserver.com PopProxy Inactive
yourmailserver.com PushNotificationsProxy Active
yourmailserver.com RpsProxy Active
yourmailserver.com RwsProxy Active
yourmailserver.com RpcProxy Active
yourmailserver.com UMCallRouter Active
yourmailserver.com XropProxy Active
yourmailserver.com HttpProxyAvailabilityGroup Active
yourmailserver.com ForwardSyncDaemon Active
yourmailserver.com ProvisioningRps Active
yourmailserver.com MapiProxy Active
yourmailserver.com EdgeTransport Active
yourmailserver.com HighAvailability Active
yourmailserver.com SharedCache Active
2. Set-ServerComponentState -Identity <yourmailserver.com> -Component PopProxy -Requester HealthAPI
-State Active
3. Get-ServerComponentstate -Identity <yourmailserver.com>
Server Component State
yourmailserver.com ServerWideOffline Active
yourmailserver.com HubTransport Active
yourmailserver.com FrontendTransport Active
yourmailserver.com Monitoring Active
yourmailserver.com RecoveryActionsEnabled Active
yourmailserver.com AutoDiscoverProxy Active
yourmailserver.com ActiveSyncProxy Active
yourmailserver.com EcpProxy Active
yourmailserver.com EwsProxy Active
yourmailserver.com ImapProxy Active
yourmailserver.com OabProxy Active
yourmailserver.com OwaProxy Active
yourmailserver.com PopProxy Active
yourmailserver.com PushNotificationsProxy Active
yourmailserver.com RpsProxy Active
yourmailserver.com RwsProxy Active
yourmailserver.com RpcProxy Active
yourmailserver.com UMCallRouter Active
yourmailserver.com XropProxy Active
yourmailserver.com HttpProxyAvailabilityGroup Active
yourmailserver.com ForwardSyncDaemon Active
yourmailserver.com ProvisioningRps Active
yourmailserver.com MapiProxy Active
yourmailserver.com EdgeTransport Active
yourmailserver.com HighAvailability Active
yourmailserver.com SharedCache Activ
Replace yourmailserver.com with your server host name.
Thanks

HT3275 Time Machine gave me this message after updating to Mountion Lion "The network backup disk does not support the required AFP features."

After upgrading to Mountain lion, I got this message when it tried to backup to "MybookLive" network disk.
"The network backup disk does not support the required AFP features."
What are AFP features and why can I now not back up to my network disk?

I had a similar issue when I tried to do a network-share backup w Time machine when the share was on a Leopard OSX G5 Power PC.
I think Time Machine looks for a minimum feature set support from the afp mounted drives so they can be used with Time Machine.
Western Digital may have to update the firmware on your device to support the new afp features.
Hope this helps.

Lock screen does not support the new panoramic feature in iOS7

Lock screen does not support the new panoramic feature in iOS7.
You are supposed to be able to take panoramic photos and then set them as your lock screen background.
Then you can move your phone around to see the full photo.
My i5 doesn't !!!!!!!!!!!!!!!!

I believe this was removed in the later betas of IOS 7. It may make a reappearance in a future update.
It was mentioned at WWDC when iOS 7 was announced, but there is no mention of it on the Apple website.

HT3275 Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. Could not complete backup to media share. The network backup disk does not support the required AFP feat

Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. "Could not complete backup to media share. The network backup disk does not support the required AFP features." What are AFP features and how do I get Time Machine to backup to my current external backup?

This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

010SM: ...does not support the initial proposed set of capabilities...

Similar Messages

Maybe you are looking for