Users created 6 hours into the future...

[clintonG]

On an XP Pro machine with a current and synchronized system time GMT
(-06:00) Central Time my use of the Visual Studio 2005 Website
Administration Tool (WAT) is writing users into the SQL Server DevEdition
twice and recording them 6 hours into the future.

The wierd time is occuring whether I use the WAT to add a user or the VS2005
CreateUserWizard control. The redundant second instance of a user occurs
when I add an existing user to a Role.

I've been posting about this for over a week. I have no clue. This is too
freakin' wierd and I wonder if anybody has any idea how to resolve this or
can help explain what is going on as it certainly sounds insane to suggest
this is "by design."

<%= Clinton Gallagher

[Greg Burns]

Clinton,

Can you duplicate this behavior on a "clean" machine? AFAIR, you mentioned
your development machine had a beta versin on it prior to the RTM.
Shouldn't be an issue, buy you never know.

I would attempt to duplicate myself, but I haven't even started to use WAT
and wouldn't know where to begin. :)

Greg
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:eb**************@TK2MSFTNGP14.phx.gbl...

On an XP Pro machine with a current and synchronized system time GMT
(-06:00) Central Time my use of the Visual Studio 2005 Website
Administration Tool (WAT) is writing users into the SQL Server DevEdition
twice and recording them 6 hours into the future.

The wierd time is occuring whether I use the WAT to add a user or the
VS2005 CreateUserWizard control. The redundant second instance of a user
occurs when I add an existing user to a Role.

I've been posting about this for over a week. I have no clue. This is too
freakin' wierd and I wonder if anybody has any idea how to resolve this or
can help explain what is going on as it certainly sounds insane to suggest
this is "by design."

<%= Clinton Gallagher

[clintonG]

Hello Greg,

I've started to prepare my resources for a fresh install to a clean disk but
you know how time consuming that is and yes, the former instance of Beta 2
is likely the culprit but on occassion a simple solution resolves these
problems. Its finding the simple solution that can be time consuming.

For example, SQL Server 2005 did not want to install either. It kept bombing
out after not being able to resolve COM+ check warnings. It took me a week
to find a solution which was very simple but again, a mystery until I found
somebody who had blogged about an arcane issue such as the one causing setup
to fail in the way it was failing for me.

So... while I'm preparing for a new install I thought I'd keep bombing the
newsgroups hoping to get lucky before I throw in the towel and take the
final step.

You know what's going to happen then don't you? The day after I get a whole
new development environment set up somebody will say "Hey I figured out why
the WTA is writing redundant user data and time stamping 6 hours into the
future" %-)

<%= Clinton Gallagher

"Greg Burns" <bl*******@newsgroups.nospam> wrote in message
news:OW**************@tk2msftngp13.phx.gbl...

Clinton,

Can you duplicate this behavior on a "clean" machine? AFAIR, you
mentioned your development machine had a beta versin on it prior to the
RTM. Shouldn't be an issue, buy you never know.

I would attempt to duplicate myself, but I haven't even started to use WAT
and wouldn't know where to begin. :)

Greg
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:eb**************@TK2MSFTNGP14.phx.gbl...

On an XP Pro machine with a current and synchronized system time GMT
(-06:00) Central Time my use of the Visual Studio 2005 Website
Administration Tool (WAT) is writing users into the SQL Server DevEdition
twice and recording them 6 hours into the future.

The wierd time is occuring whether I use the WAT to add a user or the
VS2005 CreateUserWizard control. The redundant second instance of a user
occurs when I add an existing user to a Role.

I've been posting about this for over a week. I have no clue. This is too
freakin' wierd and I wonder if anybody has any idea how to resolve this
or can help explain what is going on as it certainly sounds insane to
suggest this is "by design."

<%= Clinton Gallagher

[Greg Burns]

The lesson here of course, is to never to install a beta on your dev pc
without a backout plan. Ghost or Virtual PC is great for just such a
situtation.

Good luck, hopefully the solution is as "simple" as a fresh install. :^)
Greg

"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...

Hello Greg,

I've started to prepare my resources for a fresh install to a clean disk
but you know how time consuming that is and yes, the former instance of
Beta 2 is likely the culprit but on occassion a simple solution resolves
these problems. Its finding the simple solution that can be time
consuming.

For example, SQL Server 2005 did not want to install either. It kept
bombing out after not being able to resolve COM+ check warnings. It took
me a week to find a solution which was very simple but again, a mystery
until I found somebody who had blogged about an arcane issue such as the
one causing setup to fail in the way it was failing for me.

So... while I'm preparing for a new install I thought I'd keep bombing the
newsgroups hoping to get lucky before I throw in the towel and take the
final step.

You know what's going to happen then don't you? The day after I get a
whole new development environment set up somebody will say "Hey I figured
out why the WTA is writing redundant user data and time stamping 6 hours
into the future" %-)

<%= Clinton Gallagher

[clintonG]

Actually I was using VPC2004 and it was a dog on my machine. I even added
memory and performance was still not comfy so I took the plunge and
installed side-by-side. Oh well, thanks for the well wishes...

<%= Clinton Gallagher
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

The lesson here of course, is to never to install a beta on your dev pc
without a backout plan. Ghost or Virtual PC is great for just such a
situtation.

Good luck, hopefully the solution is as "simple" as a fresh install. :^)
Greg

"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...

Hello Greg,

I've started to prepare my resources for a fresh install to a clean disk
but you know how time consuming that is and yes, the former instance of
Beta 2 is likely the culprit but on occassion a simple solution resolves
these problems. Its finding the simple solution that can be time
consuming.

For example, SQL Server 2005 did not want to install either. It kept
bombing out after not being able to resolve COM+ check warnings. It took
me a week to find a solution which was very simple but again, a mystery
until I found somebody who had blogged about an arcane issue such as the
one causing setup to fail in the way it was failing for me.

So... while I'm preparing for a new install I thought I'd keep bombing
the newsgroups hoping to get lucky before I throw in the towel and take
the final step.

You know what's going to happen then don't you? The day after I get a
whole new development environment set up somebody will say "Hey I figured
out why the WTA is writing redundant user data and time stamping 6 hours
into the future" %-)

<%= Clinton Gallagher