Time issue seems odd to me

I put a secondary domain and po at a remote location - running 8.03 on Sles/Oes and moved all of the "local" users to that po.
while everything seems to run ok we have a weird time issue.
Mail into and out of the new mailboxes shows a three and a half hour time difference both in the date column in the groupwise client and in the printed header of the email.
The odd thing is that if I go to the properties of the email - the Creation date and the File date and time are both correct.
I can't see any time issues with the servers (primary or secondary) and especially something that would be 3:30 minutes off
there is a timezone difference between the pri and sec but that's just 1 hour.
Any thoughts?
As a workaround I have had my users add the creation column to see when they actually received the email as our clients have time critical projects.
Thanks
Dennis

Danita,
Thanks for the reply - Oh how I wish it were that easy - I've checked and double checked the PO object and the domain object - both say US eastern time.
If I send email from a mailbox on the secondary to the primary - everything is correct (a 1 hour time difference - Eastern to Central)
If I send mail from a mailbox on the primary to the secondary - it shows up right away, but says 3:30 minutes later than it should (in Date/Time, but not in Created)
If I send email from a mailbox on the secondary to a GMail account - the header shows the 3:30 offset, but the properties of the mail shows correctly.
I would be happy to send email from that po to anyone that wants to see for themselves.
Other than the PO Object and the DOM object - Where should I be looking for a time difference
and how would it be getting UTC minus 30 minutes - - Is there a special timezone out there for Hy Brasil?
The workstations all get their time settings from "time.windows.com" the windows default.
Thanks for looking into this - I just hope that I can get it figured out because as small of an issue that I think it is (they get their email, it just looks like it gets read before they officially receive it)
but it seems that this office uses the received time to track how long it takes them to do their work.
Dennis

Similar Messages

Daylight Savings Time issue with Palm Treo 755p/Missing Sync 6.0.6

I'm not sure where the fault is, but here's what a user sees here:
User has a Palm Treo 755p with the 1.08 software installed.
Since DST on March 14th, when he syncs the iCal information to the phone using Missing Sync 6.0.6, the information on the phone is pushed ahead one hour.
But the odd thing about it is how it shows on the phone.
User created a repeating event from March 12-20 from 9-10 a.m. called "test 9" for an example of this.
On March 12 and 13, this shows as "test 9" -- at 9:00 on the Treo
From the 14th on, it shows as: "test 9 (9 am EST)" -- but it is entered at *10:00* a.m.
What I don't know is if this is a Missing Sync issue or a Palm OS issue.
User's computer is running 10.6.2 -- and both computer and Palm are in the Eastern time zone.
I'm open for suggestions here -- is this a *Palm* issue? Or something else?
Thanks!

We "fixed" this by noticing that -- for whatever reason -- Detroit (we're in Ann Arbor, actually) shows as "Eastern Standard Time" where it seems that every other major city in the time zone (Columbus, Indianapolis, New York, Miami, Philadelphia, etc...) shows as "Eastern Time".
So we set up iCal on this computer to use New York ("Eastern Time") and all the events added to iCal after that synced properly.
I tried to add "Detroit" to the Palm, but had no luck in syncing with that. I think the "Eastern Time" thing is key. I have a Bug Report into Apple about the fact that the time zone seems wrong for us.
That said, while I could change pre-existing events from "Eastern Standard Time" to "Eastern Time" in iCal, those events did *NOT* sync to the Palm correctly.
The user had to delete/readd the events in the right "time zone" to get them to sync correctly.
I'd be curious to know if this solution (?) works for you as well.

Execution Time Issue

Help Please!!!
I've been searching for an execution time issue in our application for a while now. Here is some background on the application:
Collects analog data from a cDAQ chassis with a 9205 at 5kHz
Data is collected in 100ms chunks
Some of the data is saved directly to a TDMS file while the rest is averaged for a single data point. That single data point is saved to disk in a text file every 200ms.
Problem: During operation, the VI that writes the data to the text file will periodically take many hundreds of milliseconds to execute. Normal operation execution times are on the order of 1ms or less. This issue will happen randomly during operation. It's usually many seconds between times that this occurs and it doesn't seem to have any pattern to when the event happens.
Attached is a screenshot of the VI in question. The timing check labeled "A" is the one that will show the troubling execution time. All the other timing checks show 0ms every time this issue occurs. I simply can't see what else is holding this thing up. The only unchecked subVI is the "append error call chain" call. I've gone through the heirarchy of that VI and ensured that everything is set for reentrant execution. I will check that too soon, but I really don't expect to find anything.
Where else can I look for where the time went? It doesn't seem to make sense.
Thanks for reading!
Tim
Attachments:
Screen Shot 2013-09-06 at 9.32.46 AM.png ‏87 KB

You should probably increase how much data you write with a single Write to Text File. Move the Write to Text File out of the FOR loop. Just have the data to be written autoindex to create an array of strings. The Write to Text File will accept the array of strings directly, writing a single line for each element in the arry.
Another idea I am having is to use another loop (yes another queue as well) for the writing of the file. But you put the Dequeue Element inside of another WHILE loop. On the first iteration of this inside loop, set the timeout to something normal or -1 for wait forever. Any further iteration should have a timeout of 0. You do this with a shift register. Autoindex the read strings out of the loop. This array goes straight into the Write to Text File. This way you can quickly catch up when your file write takes a long time.
NOTE: This is just a very quick example I put together. It is far from a complete idea, but it shows the general idea I was having with reading the queue.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Write all data on queue.png ‏16 KB

[SOLVED] Yet another time issue...

Hi there,
I'm having some crazy, hair pulling, head banging UTC time issues on both my dual boot (Arch & Windows 8) desktop and single boot laptop.
I've been searching and following a mulitude of old threads and the official Wiki guide, however, I simply cannot get UTC time to stay correct between reboots. I've installed Arch a fair few times now, both before and after the switch to systemd and in dual and single boot setups and have never had time related issues like this before...
Here's a run down of the whole sorry story....
Fresh install - set time with hwclock --systohw utc as suggested in the beginners guide.
First boot - time an hour out - huh? cat /etc/adjtime and ls -l /etc/localtime - everything as it should be... UTC and symlink to /usr/share/zoneinfo/Europe/London. Nonetheless I duly follow the Time guide on the wiki, get to know timedatectl a bit, and soon after, time is set to be correct. Great.
Reboot. Time an hour out. Whaaaa??. Start googling, finding a plethora of bbs links to others with similar issues, decide to use NTP. Install, ntpd -qg. All good again. Time right. Phew...
Reboot. Nope. Arrrrgggghhhh. (Bare in mind - at this point I haven't even booted the Windows 8 disc, and I went through the exact same process on my Arch only laptop...)
More googling, thread reading. Find out that hwclock and ntp might be in conflict. Delete /etc/adjtime, reinstall tzdata, re-follow Time article to the letter and reenable NTP to start at boot.
Reboot - time is foward an hour yet again. Bang head repeatedly on desk. Then suddenly - 10 mins or so after boot - NTP kicks in, and time is magically goes back an hour to the correct time! Surely NTP should be doing this early in the boot process, not 10 minutes after? But OK, at least something is happening...
Next I dare to boot into Windows, and yup, time an hour out. Expected, but frustrating nonetheless. Add the registry tweak as suggested in the guide, and turn off the Windows time synchronisation. During which I noticed that Windows 8 time is set to UTC by default, not localtime, which is what the wiki says. Is this a Windows 8 thing?
I can't help thinking, that if this is the case, and the Wiki advise is written under the assumption that Windows time is always localtime, that perhaps this is the route of my problem....
Anyway, Windows time all good now, reboot Arch, time again wrong untill NTP finally kicks in - sigh. Reboot to Windows. Time an hour back. Gaaaahhhh - WTF?!! reset it to be correct. Try again. Same thing. Oops, forgot to mention that on each reboot, I check the BIOS clock, which remains persistently correct during the whole debarkle...
Ok, so I try without the registry hack and turn Windows sync back on. Still fucked. I try various combinations of the two, I try resetting Arch time over and over again. With NTP - late sync. With hwclock only, or both hwclock & NTP - totally fucked! Eventually, I give up on UTC in Arch, set it localtime, delete registry key, turn Windows time sync back on, and thus far all good......
TL;DR - couldn't get hwclock to set UTC time correctly across reboots. NTP worked (sort of), but after each reboot it would take ten minutes for the time to sync and the clock to move back an hour to the correct time. Localtime just works...
My question is - why is the wiki (and the timedatectl status output for that matter) - so adamant that we should use UTC? From what I can gather, as long as I boot Windows around the DST time. or manually move the clock forward or back an hour - all should be well, no? Or are there other issues that I may run into that I've missed? The thing I'm most concerned about is data corruption due to timestamp issues...
Also, why does the wiki repeatedly say that Windows uses localtime, when this doesn't appear to be the case in Eight? Does the wiki need updating or is Windows lying to me? I know which I'd put my money on ;-)
Finally can anyone explain why my time was always an hour forward after a reboot, even when the time was set correctly before, the BIOS showed the correct time, and NTP was in use?
Sorry for the crazy long posting, but this issue has been driving me totally batty!! Any light-shedding greatfully appreciated :-)
Last edited by knowayhack (2013-08-10 15:24:09)

Ok, so I set the clock back an hour in the BIOS, booted Windows - time right - YAY.
Rebooted Arch - time right. OMFG - pure joy!!!
I have to say, I still find it odd that this is how it works, and would like to confirm that things are looking as they should in the output from the following commands....
toby@archy ~ > timedatectl status
Local time: Sat 2013-08-10 15:42:56 BST
Universal time: Sat 2013-08-10 14:42:56 UTC
Timezone: Europe/London (BST, +0100)
NTP enabled: n/a
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2013-03-31 00:59:59 GMT
Sun 2013-03-31 02:00:00 BST
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2013-10-27 01:59:59 BST
Sun 2013-10-27 01:00:00 GMT
toby@archy ~ > sudo hwclock --debug
sudo: timestamp too far in the future: Aug 10 16:39:24 2013
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for toby:
hwclock from util-linux 2.23.2
Using /dev interface to clock.
Last drift adjustment done at 1376148264 seconds after 1969
Last calibration done at 1376148264 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/08/10 14:43:20
Hw clock time : 2013/08/10 14:43:20 = 1376145800 seconds since 1969
Sat 10 Aug 2013 15:43:20 BST -0.953640 seconds
Is it OK to now reinstall NTP to keep the clock in sync on Arch, and are the Windows reg tweaks still necessary on Windows 8?
Thank you guys SOOO much for all the unbelievabley speedy help on this issue - you have no idea how much this has been stressing me out!!
Last edited by knowayhack (2013-08-10 14:54:31)

Calender Time Issue

Dears ,
i already installed the following patch to set the day light saving for Egypt time zone
http://support.microsoft.com/kb/2967990
since then i figured out that when i reserve any meeting room
*at the meeting room calender : the meeting room reserved 1 hour after the specified time
*at my calender : i can see the right time i defined at my meeting request
Best Regards,

Hi Mahmoud,
Does this issue occur on Outlook or OWA?
If the issue occur on Outlook, I suggest using OWA to check whether the meeting room calendar shows up the incorrect time.
If in OWA, the meeting room calendar shows the correct time, it seems an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
Also run some switch commands to refresh the caches. Examples as below:
/sniff
/cleansharing
From the KB that you provide, I found following details. Hope you have noticed this:
To observe the change, you have to install the Fix it solution before May 15, 2014.
After you install this Fix it solution, DST will be turned off on June 28, 2014 to mark the beginning of Ramadan.
Important Make sure that you have the latest Windows Cumulative Update for your time zone and DST installed before you running this Fix it solution.
Thanks
Mavis
Mavis Huang
TechNet Community Support

What to do when time machine seems stuck on "Preparing Backup"

This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help.

Comments inline below.
Pondini wrote:
joshua raphael wrote:
This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
You may want to revisit that strategy:
A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version. But you can't do that from that backup.
Indeed!
Backing-up apps that way will also be useless in some cases. 3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well). Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
I think you're confusing each other with terminology. iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X. "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders. This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
I have tried reparing the disk using disk utility, but that didn't help.
Disk Utility changed a bit in Lion. When you select an entire disk, it only repairs the partition map, not all the volumes. You must repair each one separately.
Wow, good to know. (What a stupid change to make, for backwards compatibility, if for no other reason!)
See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
Whew. This editor makes it so hard to make comments inline. The key thing when time machine seems stuck is patience. Sometimes it needs to be left to run overnight. Unfortunately, it doesn't log or report it's progress very well.
Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress. And even so, there is very little logging indicating progress.
sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
The parts in italics will need to be adjusted. Tab completion makes this easy, e.g type
sudo tail -f /Volumes/
and hit tab, type the first few letters of the relevant volume name, hit tab...
Also, I have a hypothesis which needs testing.
I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been. I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working. After thinning the volume, it started working again.

OVM 3.0.3 Time Issues

I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC times. Their ntpdate offsets at boot were 23,375 seconds and 21,577 seconds; before this reboot, the largest ntpdate offset had been under 0.002 seconds. Due to NTP, the systems' time on the virtual servers were corrected; however, the RTC remained wrong. This was confirmed by using hwclock after soft linking /dev/rtc to /dev/rtc0.
All my 32bit PVM guests are running kernel 2.6.18-238.1.1.0.1.el5xen and I've been able to fix this issue by configuring xen.independent_wallclock = 1. However, my 64bit PVM guests are running kernel 2.6.32-200.13.1.el6uek and can't be configured with xen.independent_wallclock. The 64bit guests don't get hung when migrating between the servers; however, the time on the 64bit PVM guests still jumps by 30 minutes when I migrate between the servers. NTPD on the guest doesn't update the clock because the offset exceeds the sanity limit of 1000 seconds. I can manually fix the system time by running ntpdate; however this would be something I'd need to check after each migration, which isn't practical. I've ran "hwclock --utc -w" on the virtual servers but they're already about 20 seconds fast after less than a week.
Correct me if I'm wrong, but it's my understanding that the configuration of NTP on the virtual servers is only keeping their system times in check. If NTP isn't keeping the RTC of the virtual servers on time, then how can I ensure that my 64bit PVM guests are getting accurate time from the virtual servers when they live migrate? Or is there a way to make PVM's running kernel 2.6.32 keep time totally independent from the virtual servers?
I didn't have any time issues on guest servers prior to 3.0.3 (this includes running OVM 2.2, 3.0.1, and 3.0.2). Because I never had issues, I never looked closely to how the virtual servers were configured. Did something get changed in version 3.0.3 that would cause these time issues?

user4400470 wrote:
I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC timesWe currently have a fix in QA to fix the symlink (which you've already done, it seems), which will allow the hwclock to be set correctly on boot/reboot.

What would cause the original I Pad shut itself off while playing games or online? it is not a battery issue or time issue. When I turn it back on it goes to were I was when I was online ,but have to start games over.

What would cause the original I Pad shut itself off while playing games or online? it is not a battery issue or time issue. When I turn it back on it goes to were I was when I was online ,but have to start games over.

The original iPad has a slow processor and only 256 MB of memory so it often runs into low-memory failures.
Double click the home button and dismiss all of the recents - I do that weekly.
Then reboot by holding both the power and home buttons until the apple logo appears, ignore the red slider - I also do that weekly.
Both seem to help to reduce the low-memory faults that occur.

My time capsule seemed to have given up so I have just got a net gear router, I have no problem connecting wirelessly but when I connect an Ethernet cable it says it's connected but pages will not load

My time capsule seemed to have given up so I have just got a net gear router, I have no problem connecting wirelessly but when I connect an Ethernet cable it says it's connected but pages will not load

Do a factory reset .. nothing will be deleted from your backups and you will be able to get access to them again.
The Factory Reset Gen1-4.
Unplug your TC. Hold in reset. and power the TC back on.. without releasing reset for about 10sec. When the status light flashes rapidly; release it.
Be Gentle! Feel the switch click on. It has a positive feel.. add no more pressure after that.
TC will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.

In Lion, Time Machine seems to be perpetually running - and running slowly

Up through Snow Leopard, Time Machine did its incremental backup every hour quickly and stopped.
Since upgrading to Lion back in July, Time Machine seems be be running almost all the time - and very very very slowly. There doesn't seem to be any exessive Spotlight indexing going on anymore. That was long ago. So I don't think that's it.
Preparing for backup takes a long time. It take hours to eke through the backup itself, even if there weren't many changes, and finishing backup takes a long time.
I would say each backup, no matter how small, takes more than three hours.
At these forums there seems to be lots of discussion threads about this, and help pages linked to, but the suggested solutions seem to be a jumble, with some people saying they worked and many saying it didn't.
I did do a disk repair on the Time Machine volume just in case. And there is nothing else on that drive except for Time Machine backups. The drive is directly connected to my iMac (3.06 GHz Dual Core Duo, 12 GB RAM). While not vital, I'd rather not reformat the drive and lost all my old backups, which go back over a year. If I knew for sure that was the solution I'd do it. But in the discussions here there are people who seem to have tried that and reported back that it didn't help.
Right now it says it's backing up 3.5 MB of 132.9 MB - and taking forever to do it.
I know that since the last backup I haven't changed anywhere near 132.9 MB of data. Unless Lion is making massive behind-the-scene changes.
Something definitely seems to be wrong with Time Machine in Lion.
Have there been any additional thoughts on this? Is Time Machine just buggy in Lion?
Thanks,
doug

I feel ya, dawg, as they say. Right now I'm running a backup that has taken 43 minutes thus far. On an idle machine, it backed up 29.8 MB (17,949 files) followed by 19.5 MB (17,256 files). 12 min. for the first batch, 11 min., for the second. 13 min. of "Finishing backup" until it transitioned to "Cleaning up," which just completed after 12 min. Each backup typically goes 70–90 minutes. So backups are running for 65% – 80% of the time, if I leave TM running. I don't; instead, I turn on backups before going to bed, and turn them off on the first happy occasion when I notice that TM is idle.
TM backups have been behaving this way for about 2 months. Before that they were as speedy as Snow Leopard, for a couple of weeks. Before that they were taking 3 hours with the dreaded "Waiting for index to be ready" messge repeating for on hour or more. I fixed this latter problem by "trying everything" from http://pondini.org/TM/D2.html (a fine resource but, as you say, all over the map as all of the suggestions are).
TM in Lion is hosed. It's as simple as that.

Time issue- urgnt

HI Expert !
I m using this code .
LTIME TYPE SY-UZEIT
T1 TYPE SY-UZEIT VALUE 030000,
T2 TYPE SY-UZEIT VALUE 050000,
BUT WHEN I M USING T1 AND T2 in loop ( if statement ),ITS value r
T1 = 082000.
t2 = 131100 .
if t1(6) t2(6 )
ltime (6 ).
then ok . but in this i wont be able to make comparison in if statement
how i can resolve this time issue
i dont want to include timings between 3.00 a.m and 5.00 ,
for this i have used this code but its not updating data for any employee , is this code correct or not.
OPEN DATASET PA_FILE FOR INPUT IN TEXT MODE ENCODING DEFAULT.
DO.
READ DATASET PA_FILE INTO REC.
CLEAR WA_PUNCHES.
IF SY-SUBRC <> 0.
EXIT.
ENDIF.
WRITE: / REC.
if NOT ( WA_SCORE-LTIME GE T1 AND WA_SCORE-LTIME LE T2 ) .
AND
***( WA_SCORE-TERID NE TR3 AND
***WA_SCORE-TERID NE TR4 AND
***WA_SCORE-TERID NE TR5 AND
***WA_SCORE-TERID NE TR6 AND
***WA_SCORE-TERID NE TR7 AND
***WA_SCORE-TERID NE TR8 ) .
WA_SCORE-PERNR = REC+0(8) .
WA_SCORE-LDATE = REC+9(8) .
WA_SCORE-LTIME = REC+18(6) .
WA_SCORE-CANID = REC+25(8) .
WA_SCORE-TERID = REC+34(4) .
APPEND WA_SCORE TO IT_SCORE.
ELSE .
EXIT .
ADD 1 TO COUNT.
ENDIF .
ENDDO.
plz help me . its very imp. program .
thanks

Hi,
Pass values in quotes
T1 TYPE SY-UZEIT VALUE '030000',
T2 TYPE SY-UZEIT VALUE '050000',
Can you please check once again after making this change in debug mode, values of T1, T2 and LTIME.
ashish

Real time issue

Hi all,
Can any body plz send me some FICO real time issue on [email protected]
and plz tell me hw shld I prepare for interview
Thanks & Regards
Vaibhav

Hi Balraj,
In the normal practice, developers will try to find the similer infocube (as per the requirement) in the Business content. But always you will not be lucky to find such infocube in Business content. You need to create at your own to suite the business requirements. Regarding the characteristcs & key figure, it 's again depend on the requirements. Calculated object can be assign as key figure like. Sales qty, revenue & net sales etc. where as Dimesion (characteritcs) will be purely depends on the reporting point of view. Like Customer, Material & Sales Document type etc.
Hope this will help you !
Thanks,
Sanjiv

Time issues? time zone settings appear in two places

If you leave the default "set time and date automatically", you see the time zone support below and you can check it or uncheck. You can then set your time zone there. But if you uncheck the automatic date and time, you get another time zone choice and the default is Cupertino, of course. I wonder if that's the problem with some of these time issues.
I've since unchecked automatic date and time, set my city's time zone, then rechecked automatic. The only weirdness I've seen was with an excel spreadsheet where the time was correctly shown on my mac, but not on the iphone. Unfortunately I don't have that sheet anymore or I'd try again to see if it works now.
Just a thought.

I noticed the same thing and did the same thing you did because my time was off by several hours each time I turned the phone on...after it being off overnight. When it was off by only 1 hour I could turn the Auto OFF then 'tap' the timezone (already set to the correct city) and the time would instantly correct itself. Then I'd turn Auto back ON.
Turns out that my time issue was related to having the SIM PIN enabled. Once I disabled that, the time's been correct every day.

Real time issues

hi there,
can any one share some of the issues that have been dealt with in real time. i.e.during blue print stage, <b>especially in realisation stage</b>, final preparation stage
puhlease answer this question immediately

Hi Medasani,
Real time issue you can get it from the Sap support consultants. Hence, getting all the information is very difficult.
In what basis you are asking let me your requirements.
For Example :- Tolerance limits is has to increase to Rs.1 to Rs.100. for employees and vendor / customer. This is the issue from client.
How you will decide that to increase.
First you should understand the clinet work flow and get the approval from client end (core Team) then you have to increase meanwhile you have to decide the % also.
Oba3 /Oba2
Warm Regards,
Sivakumar Sathiyamoorthy

Communication channel availablity time issue

Hi All,
We want to schdule communication channel every mid night ,but when i tried to give the time there is a diffrence of about 6 hours .so evry time if in need to schdule need to calculate and schdule the time ,checked out the server timing it is similar to system time ,even messages in MONI also showing the correct time ,do we need to check anything in the adpter engine to correct this time diffrence.
Appreciate reply on this.
Thanks,
Madhu

Madhu
Iu2019m not sure if this is exactly your issue, but please see the following links concerning time issue in XI.
Time setting is differnt in sxmb_moni and RWB
Different time stamp in sxmb_moni and RWB
Hope this helps.
PJ

Time issue seems odd to me

Similar Messages

Maybe you are looking for