Sorry, missed a line here.
******* this is the AD number from my logs, from the lastLogonTimestamp attribute. > _____________________________________________ > From: Kern, Robert SBA > Sent: Friday, December 22, 2006 4:59 PM > To: '[email protected]' > Subject: RE: ActiveDirectory - Converting long int values ? > > Ok, it's getting interesting here :-) > > If I use your number 11666671551010024 and at Remedy devide it by 10000000 > and set it to a date/time field, I then end up with nearly the same date you > have. > ******* > lastLogonTimestamp (536870947) = 128.109.070.370.591.753 > lastLogonTimestamp (536870947) = 12.810.907.037,05917530000000000000000000000 > lastLogonTimestamp Date (536871012) = Dienstag, 19. Januar 2038 04:14:07 > > However, if using that exact number (128.109.070.370.591.753) at VB, it gives > me the right number. > > > So, it works with your number both at Remedy and VB. With the timestamp I > receive I can only convert it at VB properly, not at Remedy. > > > Huh ? :-) ... think it's about time for holidays :-) > > > Thanks again, Robert > > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Heider, Stephen > Sent: Friday, December 22, 2006 4:40 PM > To: [email protected] > Subject: Re: ActiveDirectory - Converting long int values ? > > Robert, > > Here is the Active Link log on my display only screen: > > Set Fields: lastLogonTimestamp = 11,666,671,551,010,024.0 > > Set Fields: lastLogonTimestamp = 1,166,667,155.10100240000000000000000000000 > > Set Fields: Last Logon = Wednesday, December 20, 2006 9:12:35 PM > > > Are you dividing by 10000000 or perhaps 1000000 (one less zero)? > > Look in your log file to see what is being set - it might uncover the cause. > > > Stephen > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Kern, Robert SBA > Sent: Friday, December 22, 2006 10:31 AM > To: [email protected] > Subject: Re: ActiveDirectory - Converting long int values ? > > Hello Stephen, > > tried that but somehow I end up with a date like "19.01.2038 04:14:07". > > Seems I'm doing something wrong here somehow... > > > Greetings, Robert > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Heider, Stephen > Sent: Friday, December 22, 2006 4:19 PM > To: [email protected] > Subject: Re: ActiveDirectory - Converting long int values ? > > Robert, > > If I understand your question correctly, it seems you are very close... > > I retrieve the AD long int value and store it in a Remedy Decimal field. > In the next Set Fields action divide by 10000000 and store in the same > Decimal field. > In the next Set Fields action set the Remedy Date/Time field to the value of > the Decimal field. > > HTH > > Stephen > > > ________________________________ > > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Kern, Robert SBA > Sent: Friday, December 22, 2006 10:09 AM > To: [email protected] > Subject: ActiveDirectory - Converting long int values ? > > > ** > > Hello list, > > I'm having a bit of an issue with converting MS AD's long int timestamp > values with Remedy means only. > > What works ok is displaying the value as such in Remedy decimal field > (double). For example the lastLogonTimestamp attribute may be > 128109070370591753, which is something like the 18th of December. > > What does not work at all is displaying the value in a Remedy date/time value > directly (instead of the decimal), or trying to "set fields" that value from > the decimal field into a date/time field. > > The DateAdd function can't be used at it seems too / does not work, as Remedy > does not understand those long int values (apart from that it seems that you > can't use 1.1.1601 as a DateBase - this could be cured though, by just adding > the difference from this date until for example 1.1.2000 in days - but still, > the format of the long int does not work).> > > Using VB.net the function could look like: > Dim logonsec As Double > Dim logondate As Date > Dim baseDate As Date = CDate("1.1.1601") > logonsec = (128111630542558000) / (10000000) > logondate = baseDate.AddSeconds(logonsec) > > Logondate then results in that 18th of December at VB. > > > Has someone run into this yet ? Perhaps there is another easy formula which > works for converting this values ? ...I think using the Filter API might also > work (have not tried yet). Something I wanted to avoid, as of having to > trigger a save somewhere (but would go that route anyway, if that would then > work). > > Am running the test box at 7.0.1p0 at the moment (used to be 6.3p19 this > morming), as of "SW00246651 ARServer needs some mechanism to determine > when large LOB's are fetched". But upgrading has not cured the baviour so far. > > > Thanks and happy holidays all together from Germany ! > > > Robert > > .......................................................... > Mit freundlichem Gruß / Kind regards > Robert Kern > Siemens AG > GIO IT SHS 3 BO ST > Sodener Straße 9 > 65824 Schwalbach > Germany > Tel. +49 619 687 2546 > Fax +49 619 687 792 546 > E-Mail: [EMAIL PROTECTED] > Internet: http://www.siemensvdo.com <http://www.siemensvdo.com> > > __20060125_______________________This posting was submitted with HTML in it___ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
