Permalinks Reported Incorrectly

Running Vibe 3.3
Setup
Http = 80
Https = 443
Listen = 8080
Listens = 8443
Using the NAM. Connecting on port 8080. (Used to use port mapping on the Vibe server, but this was very flakey on boot etc.)
Links in emails are fine.
See extract from Vibe Page. Notice the permalinks are set at 8080. The email, RSS etc are all okay.
Not sure if this is since Version 3.3 or as a result of using the NAM recently upgraded to 3.2.2-77
As we got filr working fine through NAM, we duplicated the setup for Vibe (Ignoring the Vibe documentation mostly). The only difference being it doesn't work unless the re-writer is enabled contrary to the doco.
Code:
Permalinks
http://vibe.ucb.com.au:8080/ssf/a/c/p_name/ss_forum/p_action/1/binderId/8412/action/view_permalink/entityType/folder/vibeonprem_url/1
http://vibe.ucb.com.au:8080/vibe/ebelcher/tasks
E-mail Addresses
[email protected]
RSS URL https://vibe.ucb.com.au/ssf/rss/list?bi=8412&ui=264&pd=9d0a2f87ea167699b845a59089673fc95756bd9d&v=1
ATOM URL https://vibe.ucb.com.au/ssf/atom/list?bi=8412&ui=264&pd=9d0a2f87ea167699b845a59089673fc95756bd9d&v=1
iCal URL https://vibe.ucb.com.au/ssf/ical/basic.ics?bi=8412&ui=264&pd=9d0a2f87ea167699b845a59089673fc95756bd9d&v=1
Does anyone have any ideas?
Thanks

Originally Posted by ucba
..You learn something everyday...
Yep, that's what keeps our occupation interesting (most times, not always )....
I usually add this to the /etc/init.d/after.local (if it does not already exist, simply create it)
#----after.local begin script
#!/bin/bash
#Redirect port incoming traffic on port 80 to 8080:
iptables -t nat -A OUTPUT -d localhost -p tcp --dport 80 -j REDIRECT --to-ports 8080
iptables -t nat -A OUTPUT -d $HOSTNAME -p tcp --dport 80 -j REDIRECT --to-ports 8080
iptables -t nat -A PREROUTING -d $HOSTNAME -p tcp --dport 80 -j REDIRECT --to-ports 8080
#Redirect port incoming traffic on port 443 to 8443:
iptables -t nat -A OUTPUT -d localhost -p tcp --dport 443 -j REDIRECT --to-ports 8443
iptables -t nat -A OUTPUT -d $HOSTNAME -p tcp --dport 443 -j REDIRECT --to-ports 8443
iptables -t nat -A PREROUTING -d $HOSTNAME -p tcp --dport 443 -j REDIRECT --to-ports 8443
#----end script
Do note that when using the $HOSTNAME environment variable, check that 'ping $HOSTNAME' returns the servers listening IP address you intend to do the redirect for.
I think integration/interaction between Vibe and NAM (or is it the other way around ) could be tighter. Still, with the settings within Vibe and for the reverse proxy set to use the same names and ports it should work without issue. Not sure it can be seen as bug, more of a limitation.
If you have good additional ideas on what you would like to see, https://www.novell.com/rms is the way to drop your idea/request/enhancement in.
Cheers,
Willem
Cheers,
Willem

Similar Messages

  • SSL peer reports incorrect Message Authentication Code (Error code: ssl_error_bad_mac_alert) after Firefox 36 Upgrade

    When upgrading from Firefox 35 to 36 (Windows 8, 32 bit) I start getting "SSL peer reports incorrect Message Authentication Code (Error code: ssl_error_bad_mac_alert)" SSL errors on at least one website I use. (https://marketplace.ibmcloud.com).
    The message only appears when I get redirected to the website again after a previous OpenID login (some more cookies are set). When I browse the website without authentication it works on the encryption without any issues.
    None of [1] applied, I do not experience this problem with any other browser or the previous version of Firefox. It seems to be limited to the specific case. Clearing any kind of cache, enable / disabled the ssl3* mechanisms, did have zero effect.
    Is there any other way to debug this or someone has an idea what changed with Firefox 36 to introduce this behavior? I downgraded back to 35 for now to work again.
    [1] https://support.mozilla.org/en-US/questions/new/desktop/fix-problems/form?search=SSL+peer+reports+incorrect+Message+Authentication+Code+(Error+code%3A+ssl_error_bad_mac_alert)&step=aaq-question

    I created a ticket there as well for them to investigate, although knowing IBM I guess we know the answer already, if I hear anything from there I will let you know.
    However, as the problem only occurs on the one version of Firefox as of right now, I'm inclined to role out potential server side issues as a reason and pass it to something within Firefox, or was there a change any encryption defaults that might force the server to switch to a different version or something that might have the bug?

  • Uptime being reported incorrectly

    Hey guys
    I have this little weird problem... I know I shoudln't be -too- concerned about uptime since my arch still works beautifully, but it's like one of those small details in a picture that keeps annoying you from far, far away until you finally explode and rant about it, if you get what I mean .
    The problem is simple: my uptime is being reported incorrectly! take a look:
    [dragon@cave ~]$ uptime
    09:57:21 up 13 min, 1 user, load average: 0.02, 0.12, 0.10
    [dragon@cave ~]$ date
    mié ago 26 09:57:22 VET 2009
    [dragon@cave ~]$
    Apparently, I turned the PC about 10 hours ago? I just turned it on 30 minutes ago! what could be happening?
    Here goes some "last" output:
    dragon tty7 :0 Wed Aug 26 09:44 still logged in
    reboot system boot 2.6.30-ARCH Wed Aug 26 09:43 (00:14)
    dragon tty7 :0 Wed Aug 26 03:26 - down (01:23)
    dragon tty7 :0 Wed Aug 26 03:25 - 03:26 (00:01)
    dragon tty7 :0 Wed Aug 26 00:25 - 03:25 (03:00)
    reboot system boot 2.6.30-ARCH Wed Aug 26 00:25 (04:25)
    dragon tty7 :0 Mon Aug 24 15:12 - down (1+07:19)
    dragon tty7 :0 Mon Aug 24 12:37 - 15:12 (02:35)
    reboot system boot 2.6.30-ARCH Mon Aug 24 12:37 (1+09:55)
    dragon tty1 Mon Aug 24 05:15 - down (01:14)
    dragon tty1 Mon Aug 24 05:15 - 05:15 (00:00)
    dragon tty7 :0 Mon Aug 24 05:04 - down (01:25)
    dragon tty7 :0 Mon Aug 24 23:14 - 05:04 (-18:-10)
    reboot system boot 2.6.30-ARCH Mon Aug 24 23:14 (-16:-44)
    dragon tty7 :0 Mon Aug 24 03:53 - crash (19:20)
    dragon tty7 :0 Mon Aug 24 03:29 - 03:53 (00:24)
    dragon tty7 :0 Mon Aug 24 03:28 - 03:29 (00:00)
    dragon tty7 :0 Mon Aug 24 03:27 - 03:28 (00:00)
    dragon tty7 :0 Mon Aug 24 03:22 - 03:27 (00:05)
    dragon tty7 :0 Mon Aug 24 03:15 - 03:22 (00:06)
    dragon tty7 :0 Mon Aug 24 03:15 - 03:15 (00:00)
    dragon tty1 Mon Aug 24 03:15 - crash (19:59)
    dragon tty1 Mon Aug 24 03:15 - 03:15 (00:00)
    dragon tty7 :0 Mon Aug 24 03:14 - 03:15 (00:00)
    dragon tty7 :0 Mon Aug 24 19:30 - 03:14 (-16:-16)
    dragon tty7 :0 Mon Aug 24 19:30 - 19:30 (00:00)
    dragon tty7 :0 Mon Aug 24 18:57 - 19:30 (00:32)
    dragon tty1 Mon Aug 24 18:55 - 18:56 (00:01)
    dragon tty1 Mon Aug 24 18:55 - 18:55 (00:00)
    dragon tty7 :0 Mon Aug 24 18:53 - 18:57 (00:03)
    dragon tty1 Mon Aug 24 18:52 - 18:53 (00:00)
    dragon tty1 Mon Aug 24 18:52 - 18:52 (00:00)
    dragon tty7 :0 Mon Aug 24 17:30 - 18:53 (01:23)
    dragon tty7 :0 Mon Aug 24 17:29 - 17:30 (00:00)
    dragon tty1 Mon Aug 24 17:29 - 17:29 (00:00)
    dragon tty1 Mon Aug 24 17:29 - 17:29 (00:00)
    dragon tty7 :0 Mon Aug 24 17:25 - 17:29 (00:03)
    dragon tty7 :0 Mon Aug 24 17:23 - 17:25 (00:01)
    dragon tty7 :0 Mon Aug 24 16:53 - 17:23 (00:30)
    dragon tty7 :0 Mon Aug 24 16:52 - 16:53 (00:00)
    reboot system boot 2.6.30-ARCH Mon Aug 24 16:51 (-10:-21)
    dragon tty2 Mon Aug 24 16:41 - down (00:09)
    dragon tty2 Mon Aug 24 16:41 - 16:41 (00:00)
    dragon tty1 Mon Aug 24 16:40 - down (00:09)
    dragon tty1 Mon Aug 24 16:40 - 16:40 (00:00)
    reboot system boot 2.6.30-ARCH Mon Aug 24 16:40 (00:09)
    dragon tty2 Mon Aug 24 04:57 - 05:13 (00:15)
    dragon tty2 Mon Aug 24 04:57 - 04:57 (00:00)
    dragon tty2 Mon Aug 24 04:52 - 04:56 (00:04)
    dragon tty2 Mon Aug 24 04:52 - 04:52 (00:00)
    dragon tty1 Mon Aug 24 04:50 - down (00:40)
    dragon tty1 Mon Aug 24 04:50 - 04:50 (00:00)
    root tty1 Mon Aug 24 04:48 - 04:49 (00:01)
    root tty1 Mon Aug 24 04:48 - 04:48 (00:00)
    reboot system boot 2.6.30-ARCH Mon Aug 24 04:48 (00:41)
    dragon tty2 Mon Aug 24 04:33 - down (00:13)
    dragon tty2 Mon Aug 24 04:33 - 04:33 (00:00)
    dragon tty1 Mon Aug 24 04:29 - down (00:18)
    dragon tty1 Mon Aug 24 04:29 - 04:29 (00:00)
    root tty1 Mon Aug 24 04:28 - 04:29 (00:01)
    root tty1 Mon Aug 24 04:28 - 04:28 (00:00)
    reboot system boot 2.6.30-ARCH Mon Aug 24 04:27 (00:19)
    About details... well, it's a desktop PC and I never suspend or hibernate it...
    Any ideas guys? if you need any more info just say, I don't know what else is needed to help solve the problem
    Thanks in advance!
    - DARKGuy
    Last edited by DARKGuy (2009-08-26 14:37:43)

    AHH... huh, y'know, I think I should do a backflip and kick myself in the back for having overlooked that up and created this thread XD...
    /me hides in shame
    Thank you guys ;;
    Last edited by DARKGuy (2009-08-26 14:41:13)

  • Why are DWDM XFP tunables reporting incorrect wavelength channels?

    Why are the channel numbers output from "show controllers tenGigE <port> phy" reporting incorrect channels?
    I have seen this in IOS XR 4 and 5 now. The channel is incorrect but the tuned wave is correct and the channel appears correct in the configuration.
    I searched for caveats but found nothing... Am I just overlooking something?
    RP/0/RSP0/CPU0:ios(config)#int tenGigE 0/1/0/0
    RP/0/RSP0/CPU0:ios(config-if)#shut
    RP/0/RSP0/CPU0:ios(config-if)#controller dwdm 0/1/0/0
    RP/0/RSP0/CPU0:ios(config-dwdm)#admin-state maintenance
    Wed Mar  5 11:29:49.698 UTC
    Maintenance will be Forced one if it is disabled for this port. You may first verify the status by the show interfaces command.
    RP/0/RSP0/CPU0:ios(config-dwdm)#commit
    Wed Mar  5 11:29:50.818 UTC
    RP/0/RSP0/CPU0:ios(config-dwdm)#wavelength 55
    RP/0/RSP0/CPU0:ios(config-dwdm)#commit
    Wed Mar  5 11:29:58.577 UTC
    RP/0/RSP0/CPU0:ios(config-dwdm)#admin-state in-service
    RP/0/RSP0/CPU0:ios(config-dwdm)#commit
    Wed Mar  5 11:30:05.217 UTC
    RP/0/RSP0/CPU0:ios(config-dwdm)#int tenGigE 0/1/0/0    
    RP/0/RSP0/CPU0:ios(config-if)#no shut
    RP/0/RSP0/CPU0:ios(config-if)#commit
    Wed Mar  5 11:30:13.810 UTC
    RP/0/RSP0/CPU0:ios(config-if)#exit
    RP/0/RSP0/CPU0:ios(config)#exi
    RP/0/RSP0/CPU0:ios#
    RP/0/RSP0/CPU0:ios#
    RP/0/RSP0/CPU0:ios#show controllers tenGigE 0/1/0/0 phy | begin Signal
    Wed Mar  5 11:30:32.570 UTC
            Signal Condition Control: Normal Async REFCLK,
            Thresholds:                    Alarm High         Warning High          Warning Low            Alarm Low
                  Temperature:               73.000                70.000                -5.000                -8.000
                      Voltage:           0.000 Volt            0.000 Volt            0.000 Volt            0.000 Volt
                         Bias:         85.000 mAmps          72.000 mAmps          10.000 mAmps           5.000 mAmps
               Transmit Power:  3.981 mW (6.00 dBm)   2.512 mW (4.00 dBm)   0.794 mW (-1.00 dBm)   0.501 mW (-3.00 dBm)
                Receive Power:  0.398 mW (-4.00 dBm)   0.251 mW (-6.00 dBm)   0.002 mW (-27.96 dBm)   0.001 mW (-30.00 dBm)
            Laser First Frequency: 191 THz, 950.000 GHz
            Laser Last Frequency: 196 THz, 0.000 GHz
            Laser Min Grid Spacing: 50.000 GHz
            Wavelength Control: setpoint=1550.05 nm, error=0.00 nm
            FEC Control: amplitude_threshold=50.00%, phase_setpoint=50.00%
            Temperature: 42.949
            Voltage: 0.000 Volt
            Tx Bias: 20.654 mAmps
            Tx Power:  1.413 mW (1.50 dBm)
            Rx Power:  0.000 mW (<-40.00 dBm)
            Control Status: Module NR, Interrupt, Rx LOS,  Rx not ready, Rx CDR not locked,
            Wavelength Channel: 30
            Wavelength Error: 0.000 GHz

    1)
    CLI configures XR Channel. 
     'wavelength 55' maps to Wavelength '1550.116 nm'
    The following CLI gives CLI mapping to Wavelength (nm).
    RP/0/RSP0/CPU0:RR03#sh controllers dwdm 0/1/0/0 wavelength-map 
        55    6               193.40          1550.116
    2) 
    SW translates configured 'wavelength <channel number>' to 
    Optics Channel number (30) to get Wavelength 1550.05 nm.
    RP/0/RSP0/CPU0:ios#show controllers tenGigE 0/1/0/0 phy | begin Signal
            Laser First Frequency: 191 THz, 950.000 GHz
            Laser Last Frequency: 196 THz, 0.000 GHz
            Laser Min Grid Spacing: 50.000 GHz
            Wavelength Control: setpoint=1550.05 nm, error=0.00 nm
            FEC Control: amplitude_threshold=50.00%, phase_setpoint=50.00%
            Temperature: 42.949
            Voltage: 0.000 Volt
            Tx Bias: 20.654 mAmps
            Tx Power:  1.413 mW (1.50 dBm)
            Rx Power:  0.000 mW (<-40.00 dBm)
            Control Status: Module NR, Interrupt, Rx LOS,  Rx not ready, Rx CDR not locked,
            Wavelength Channel: 30
            Wavelength Error: 0.000 Ghz
    3)
    Instead we recommend our customers to use the following CLI which gives option to 
    Configure wavelength in 'nm'. 
    RP/0/RSP0/CPU0:RR03(config-dwdm)#wavelength update ?
      <1528773-1568362>  Enter 7-digit Wavelength data; e.g. 1532290 for 1532.29 nm
    Available wavelength is given by this CLI. 
    RP/0/RSP0/CPU0:RR03#sh controllers dwdm 0/1/0/0 wavelength-map 

  • FRSM Randomly Reports Incorrect Quota Usage

    We are using Server 2008 with FSRM 6.1 and are randomly seeing some quotas reporting incorrectly that they are at 100%. If the folder is checked they are well under the quota but FRSM still reports it as 100% even after a refresh.
    The only way that I have seen the quotas reporting as normal is when we delete them and recreate them but it returns a few weeks later.
    This is only happening on one file server (we have several that FRSM manages the quota allocations for) and disk compression has not been turned on for that volume. This also is not happening to every quota on that volume, only some.
    Any ideas?

    Hi,
    Firstly, please refer to the thread to check if the disk usage of the folder is reported correctly:
    Server 2008R2 reports disk size/free space incorrectly in explorer and disk manager
    http://social.technet.microsoft.com/Forums/en-US/bf5445d5-e796-4cbb-9571-8639b900cfd4/server-2008r2-reports-disk-sizefree-space-incorrectly-in-explorer-and-disk-manager?forum=winserverfiles
    Then check if your current account have permissions to access subfolders. If the user does not have permission to access all subfolder. The size of some folders will not be counted with right click on a folder.
    FSRM usage quota incorrect after deletion of 'RECYCLER' folder
    http://social.technet.microsoft.com/Forums/en-US/4a076bd3-6e84-4392-9d1a-d93e67a9c319/fsrm-usage-quota-incorrect-after-deletion-of-recycler-folder?forum=winserver8gen
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Portal component information reporting incorrect version

    Dear all,
    Has anyone experienced that the portal content information (http://hostname:port/monitoring/ComponentInfo)is reporting incorrect information? We have installed XSS 603 components and the summary part does not reflect that , but the details does.
    Its also not reporting SAPPCUI_GP in the software component part. Has anyone seen this and whats the fix?
    Thanks!
    Neeta

    HI Shanti,
    I followed the intructions in note # 910073 and all worked fine. However, the version information is still not reported correctly. component information is reporting ESS600 and we have ESS603 installed & no PCUI component is reported but the details show that its deployed.?
    Does the portal need to be restarted after the change in note 910073?
    Regards, Neeta

  • MCE5 etc report incorrect purchase value/quantity

    We have found what we would consider a fault with the logistics information system for MM, such that the MCE5 family of reports will give misleading or incorrect information.
    The problem arises if you modify an existing PO item.  In our case we were splitting an old item so that the remaining delivery quantity was assigned to a different cost object.  The new item is recorded in S012 with the current date/period, but the corresponding reduction in the old item is recorded against the original creation date of that item. Hence, even though the net change in the PO this period is zero, MCE5 reports a positive purchase value (in our case several £100k over a few items).
    If you run the report over all periods, the total purchase value remains unchanged, but if you are looking at recent purchase values (say last 3 or 6 months), then when the original item date drops off the start of this period, you get a misleading increased value.
    The same situation would arise if you were to amend such an item to say increase the quantity required.  MCE5 will only report this increased purchased value in the period the item was originally created, rather than the current period.
    I cannot imagine any circumstance when anyone would want the result that standard SAP gives.  SAP replied to my query under OSS as follows:
    "I'm sorry that this doesn't meet your business requirements. We really
    haven't had complaints from other customers. The rule for update of
    PO value in S012 is defined in transction MC26 as BEDAT. The period
    of the creation date will always be updated regardless of when you
    make the change. This is not customizable in standard. I guess you could
    control this in a user exit by changing the BEDAT, but it might lead to
    problems and confusion later. I wouldn't recommend it, since MM-PUR
    development couldn't support it. You are requesting a design change,
    which isn't handled by development support. You can always enter a
    development request with your solution manager, but at the moment we
    have no plans for changing this design. It also works the same in BW."
    Has anyone else come up against this?
    Has anyone found a solution?
    Or has anyone got an alternative method to get similar figures to that reported in MCE5 etc but without this failing?
    Any help gratefully received...

    Dear you!
    I also meet the issue. I think everybody can tell ours about mean of FI value column, PCA value column in KEAT.
    Help me to process the issue.
    Best regards, Huy!

  • Filter values in report incorrect

    Hi All
    The are incorrect filter values being shown for the field Purchase document number (0OI_EBELN) when i right click and select filter value. Values such as 1, 2, 3, 4, so on upto 999 are present in the selection screen. But these values are not present in the underlying data provider. The infoobject 0OI_EBELN does not have master data or texts table associated with it. Can u please help me out in finding this one ....
    With Regards,
    Hari

    Hi Hariharan,
    Goto Change mode of the Infoobject- Business Explore tab Query Def. Filter Value Selection-- Select Valules in Master Data Table-- Activate.
    Now try executing the report.
    Hope this helps.
    Veerendra

  • Fascinate Reporting Incorrect Cell Strength

    I have been watching the Signal Strength from Settings > About > Status and noticed the reported numbers do not correlate with the Cell Bar Level display at the top or the numbers I am logging with the Cell Connectivity Tracker application.
    Here are some observations from using the "Cell Connectivity Tracker" application:
    Cell strength as it relates to the Cell Signal Bars
    0 bars = -106dBm
    1 bar = -101dBm
    2 bars = -96dBm
    3 bars = -91dBm
    4 bars = -86dBm
    Right now I have no visible Bars being displayed and my Signal Strength is -72dBm on the Status page and the Cell Connectivity Tracker logged -106dBm. My phone even went to 1x (xRTT).
    My phone is constantly changing from -101(dBm) and -106(dBm), constantly jumping between Cell Locations and reporting Physical Link Down. My TWAS (Time without a signal) was 61% for 1h 7m. I'm also less than 1/2 mile from a VZW tower.
    Speed Test #1 was 159kbps D/L and 224kbps U/L.
    Speed Test #2 was 118kbps D/L and 365kbps U/L.
    Speed Test #3 was 50kbps D/L and 469kbps U/L.
    Something is definitely not correct with the cell signal strength reporting on the Fascinate.
    What if the phone's software is reporting a higher signal than what is actually being received and this incorrect information is being used to make operating system/network connectivity decisions? Might this cause all types of issues from lagging, slow data performance and bad battery life? I find it very strange that all three signal strength measurements are reporting different values.
    What if a significant number of Fascinates have cell strength issues, wouldn't this support some type of "electronics lemon law"?
    I am on my second Fascinate and both have exhibited the same symptoms. My wife's Fascinate is having issues too.
    Other Samsung Galaxy S phone users don't seem to be as vocal about the battery, cell strength and lag issues. This makes me wonder if the Fascinate really does have a design/hardware issue. To top it off, the Fascinate is one of the last Galaxy S phones to receive Froyo. Maybe the supposed "issue" is causing problems with the developer testing of Froyo?
    Just thinking things through,
    Tim

    Hardware version = i500.04
    Firmware version = 2.1-update1
    Baseband version = S:i500.04 V.EA28
    Kernel version = 2.6.29
    Build number = SCH-I500.EA28
    RealSignal Bars vs Signal Strength
    0 bars = -106dBm
    1 bar = -101dBm
    2 bars = -96dBm
    3 bars = -91dBm
    4 bars = -86dBm
    Same scale as Cell Connectivity Tracker
    Signal Strength from Settings > About > Status fluctuates, but doesn't match the visual Bars at the top.  For example, the visual Bars at the top display zero (no signal), but Settings > About > Status - Signal Strength of -76dBm.
    Thanks,
    Tim

  • Fixing or reporting incorrect character glyphs?

    On my Macbook Pro (up to date according to Software Update), I've found a number of UTF-8 character codes that display as the wrong glyph with some software (but usually other software gets it right).  I've tried to find a way of either submitting a bug report to get it fixed, or maybe fixing  it myself, but I've been unable to find any information about how to do this.  Is it possible?  If so, how?
    An example from this morning:  I found that the char U+FA1B (福, which displays incorrectly in this window) is displayed as the glyph for U+798F (福, which is probably correct if you have Unihan charsets installed).  These are a traditional/simplified pair ("blessing, happiness") that differ in the left "radical" portion.  What's especially weird is that for some apps, if I copy the FA1B char, it gets translated to 798F.  Others, such as my Terminal to the right of this one, display the 798F glyph for both, though if I cut out a line of text and feed it to "od -x", I do see the correct hex bytes for both chars (3E5BE7, A68FEF).
    One bit of bizarreness:  If I look these chars up in Character Palette, the "Character Info" panel displays them both correctly.  But if I open the Font Variation panel, both characters includes a few fonts that show the wrong glyph.  Thus,  for FA1B, there are 13 fonts shown, 12 correct, and one (Arial) showing the 798F glyph.  For 798F, there are 27 fonts shown, of which 3 (PCMyungjo, AppleGothic, Arial) are the FA1B glyph, and the other 24 are correct.
    Does anyone know what might be going on here?  Is this the wrong forum to find an answer?  If so, is there some place I can ask about it where people will be interested in helping get it fixed?  If so, how could I have found it without bothering this group?
    (Out of  curiosity, I pulled out my G1 phone, fired up its browser, and had it show a doc that contains these two characters.  It displayed them fine, as it has with earlier example like this. ;-)

    jc1742 wrote:
    One bit of bizarreness:  If I look these chars up in Character Palette, the "Character Info" panel displays them both correctly.  But if I open the Font Variation panel, both characters includes a few fonts that show the wrong glyph.  Thus,  for FA1B, there are 13 fonts shown, 12 correct, and one (Arial) showing the 798F glyph.  For 798F, there are 27 fonts shown, of which 3 (PCMyungjo, AppleGothic, Arial) are the FA1B glyph, and the other 24 are correct.
    The glyph which is displayed at any particular time depends on the font which is being used by the app or OS, which could depend on a variety of factors.  The "Arial" that you mention is Arial Unicode, which is ancient and not something anyone should use for Han unless there were no alternative.  You could complain to Microsoft, but I don't think anybody is ever going to fix any bugs that font has.  PCMyungjo and Apple Gothic are older Apple fonts intended only for Korean, not Chinese or Japanese.  You could send feedback to Apple about them, but as the use of Han characters in Korean is now extremely limited I doubt fixing the font would have much priority, assuming that they are in fact wrong for that language.
    I guess if you removed those fonts there is no chance any app could use the wrong glyphs.  You might want to at least make sure that Korean is listed below Chinese and Japanese in system prefs/language & text/language.  That should ensure the right glyphs appear in normal Han contexts (assuming Arial Unicode is never used, which hopefully is the case).

  • Image size reported incorrectly

    We have a studio where we shoot 1080p (1920x1080 resolution). When we upload these files into Final Cut Server the Image Size column usually (but not always) reports that the Image Size is 1440x1080. This was really concerning me, but when I export the video back to my computer the original media is still 1920x1080. The poster frame image is also still 1920x1080.
    Any ideas why FCS is reporting the incorrect Image Size most of the time?

    Philip Hodgetts wrote:
    I've been under the impression that DVCPRO HD in 60 Hz countries is 1280x 1080 for nominal "1080" files. In 50 Hz countries it's 1440 x 1080.
    Philip
    That is indeed correct. Good point. Are you working in 50i, bradleylamar?

  • Times in various apps reported incorrectly in iOS7

    The current time in apps such as calendar, mail, dijit remote, and weather appears incorrectly in iOS7. This seems to occur sporadically. I have checked settings>general>date&time and the phone is set to 12 hour format, set automatically is on, and time zone is New York which is correct. Location services for these apps is set to on. I have also tried a soft reset of the phone. Is anyone else experiencing this bug?
    I have noticed several bugs (this being one of many that I am reporting) since upgrading to iOS7 which has been very disappointing. I am a huge Apple advocate and this has not been the experience of "It just works" that I have come to expect from my Apple products. It is because I care so much about the Apple ecosystem that has made my work and play so much more enjoyable that I will take the time to report these in hopes that Apple will take notice and that subsequent updates will address these issues. 

    Trying logging into FaceTime instead.
    I was having this issue as well and tried many times to get iMessage to authorize.
    I kept getting the "check your network connection" error.
    I went to my FaceTime preferences and noticed it was "waiting for authorization" as well.
    When I logged in under FaceTime my ID &amp; Password were accepted.
    Then I returned to iMessage and I was logged in there as well.
    Seems like the FaceTime setting was able to override the glitch in iMessage.
    See if that works for you too.

  • Backup status reported incorrectly

    Using Windows SBS 2008, following recreating a partition (D:) which had reverted to RAW from NTFS, I needed to restore the last good backup, which appeared from the SBS Console/Server Backup Properties/Previous Backups to have successfully backed up drives
    C: and D:.  When moving to restore, I find that this backup was completed with warnings.  Expanding this line, it reports an error: "D: Incorrect function".  When I look back through the history of the connected backup drive,
    I find that it has only backed up the C: drive even though the backup configuration has always been set to back up both C: and D:.  As D: drive is the drive which holds all of the data, everything appears to be lost!  Is there any way to recover
    any of this data?

    Using Windows SBS 2008, following recreating a partition (D:) which had reverted to RAW from NTFS, I needed to restore the last good backup, which appeared from the SBS Console/Server Backup Properties/Previous Backups to have successfully backed up drives
    C: and D:.  When moving to restore, I find that this backup was completed with warnings.  Expanding this line, it reports an error: "D: Incorrect function".  When I look back through the history of the connected backup drive, I find that
    it has only backed up the C: drive even though the backup configuration has always been set to back up both C: and D:.  As D: drive is the drive which holds all of the data, everything appears to be lost!  Is there any way to recover any of this
    data?
    Why does SBS Console report backup as successful when it appears that it is NOT successful?

  • Airport Extreme 802.11n reports incorrect Locale and Country Code

    I have just replaced my MacBook Pro CoreDuo's Airport Extreme card with a Mac Pro one that gives excellent throughput with 802.11n but, depending upon which channel it connects to the wireless router, System Profiler displays a weird selection of locales and country codes (e.g. locale: RoW, country code X2) .... perhaps this does't matter ... perhaps it does as other threads here report not being able to make a connection when an available channel is supposed not to be available in the incorrectly reported country.
    What controls this (incorrect) choice and how can it be fixed?
    System Profile of en1:
    Card Type: AirPort Extreme (0x14E4, 0x88)
    Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.19)
    Locale: RoW
    Country Code: X2
    Supported PHY Modes: 802.11 a/b/g/n

    AirPort-Guy wrote:
    The Locale is programmed into the card. If you bought your Mac Pro in a country other than where you are currently living, and you are using the card that came with it, you could be violating your country's wireless regulations.
    Actually this is not entirely correct.
    Rather the Mac sets its AirPort country code based upon the first beacon packet containing regulatory domain information received when the Mac starts passively listening to incoming packets after the AirPort interface is enabled.
    RoW does stand for "rest of world" and the "X" domains are temporary used ones when searching for regulatory domain information.
    So if you're seeing your Mac's AirPort card programmed to a different country code regulatory domain than it should be, it's because someone near you is using an illegal wireless access point/router.

  • Intrastat reporting- Incorrect PO picked

    Hi Gurus,
    I need to find out why and how a particular PO is being picked by the MEIS report? I was always in the belief that once the import procedure is maintained at the PO item level, if any GR/ IR takes place, then these would be reported. But I am not able to understand, while even after removing the import data in a PO, it is being picked. Pls could you throw some light on this. Your timely help would be much appreciated.
    Thanks
    Madan

    How could you delete the import data?
    You probably deleted a value in the import data of the PO. But this does not make the import data going away.
    First of all you define in customizing when the import screens are coming up.
    Usually when you and your vendor belong both to a different  country in the EU.
    Then, the PO is subject for Intrastat reporting.
    But reported are only x-border movements.
    The PO is not picked if the movement (good receipt has not yet been posted.
    But once you have a movement, then it depends further if the invoice receipt happened in the same month .
    If yes then the movement is selected for the report.
    If not, dependend on local country laws, the movement is either valuated with PO price, or not reported in this month. Then it will be reported in next month, either with the invoice value (if the Invoice wil be received in the meantime) or with PO price if the inovice is still not received.
    Why would you like to exclude this PO and its movements from Intrastat? Why dont you exclude the PO number directly from the selection screen in MEIS?

Maybe you are looking for