ADMT 3.0 Users Migration: Fix Users' Group Memberships stopped working

We have been using ADMT 3.0 for the last 2 months to migrate users from a
Windows 2000 to a Windows 2003 R2 Active Directory (native). All groups (with
SidHistory) were migrated before any users were migrated. Then as each office
was migrated the users were migrated (with SidHistory) with the 'Fix users's
group memberships' option selected which successfully updated group
memberships. Note: We are not migrating domain BUILTIN groups.

All this worked fine until last week when group memberships failed to
update. The user would migrate successfully but the user would not be added
to the relevant groups. Verifyied that all groups existed in the new AD and
checked the ADMT migration logs but no errors found except, to comment that
the groups the user should be members of already existed in the new AD (also
shown in logs when it worked). I increased ADMT logging from 3 to 7 (verbose)
but this did not show any more detail. The ADMT examines and detects a user
is a member of x number of groups but does not update.

Is anyone else had this issue with ADMT version 3.0 or any suggestions on
how to fix. I noticed a few artcles with similar issues with ADMT 2.0 but the
fix was to install a hiotfix to replace a couple of DLLs which, with ADMT 3.0
are later versions anyway.

We have managed to migrate approx. 400 users without issues and there is
approx. another 1200 to migrate.

Thanks and regards,

Jason

Performed a SQL repair of the ADMT database which , found zero allocation
errors and consistency errors but resolved the issue!
--
Thanks and regards,

Jason


"Jason" wrote:

> We have been using ADMT 3.0 for the last 2 months to migrate users from a
> Windows 2000 to a Windows 2003 R2 Active Directory (native). All groups (with
> SidHistory) were migrated before any users were migrated. Then as each office
> was migrated the users were migrated (with SidHistory) with the 'Fix users's
> group memberships' option selected which successfully updated group
> memberships. Note: We are not migrating domain BUILTIN groups.
>
> All this worked fine until last week when group memberships failed to
> update. The user would migrate successfully but the user would not be added
> to the relevant groups. Verifyied that all groups existed in the new AD and
> checked the ADMT migration logs but no errors found except, to comment that
> the groups the user should be members of already existed in the new AD (also
> shown in logs when it worked). I increased ADMT logging from 3 to 7 (verbose)
> but this did not show any more detail. The ADMT examines and detects a user
> is a member of x number of groups but does not update.
>
> Is anyone else had this issue with ADMT version 3.0 or any suggestions on
> how to fix. I noticed a few artcles with similar issues with ADMT 2.0 but the
> fix was to install a hiotfix to replace a couple of DLLs which, with ADMT 3.0
> are later versions anyway.
>
> We have managed to migrate approx. 400 users without issues and there is
> approx. another 1200 to migrate.
>
> Thanks and regards,
>
> Jason

[axplains]

Hello,
I had exactly the same problem.

Since I am not a SQLserver expert, can you please explain how to do a SQL repair of the ADMT database?
Thank you in advance.

Axplains

I performed SQL repair on an ADMT server which was using SQL Express 2005 as
follows;

1)Logon to Microsoft SQL Server Management Studio Express (download from
Microsoft if not installed).
2)Select the ADMT database and put the ‘Admt’ database into emergency mode
by running: ALTER DATABASE admt SET EMERGENCY.
3)Put the ‘admt’ database into single user mode like by running: ALTER
DATABASE admt SET SINGLE_USER
4)Run: DBCC checkdb(admt, REPAIR_ALLOW_DATA_LOSS)
If all goes well, you will not see any error messages and the db will be in
a good state.
5)Put the ‘admt’ database back into multi-user mode so it can be used for
production: ALTER DATABASE admt SET MULTI_USER

Note: Where 'admt' is shown in the above commands replace with your ADMT
database name if different.

The above procedure should work for full SQL server product.

Hope this fixes it.

Jason


"axplains" wrote:

>
> Hello,
> I had exactly the same problem.
>
> Since I am not a SQLserver expert, can you please explain how to do a
> SQL repair of the ADMT database?
> Thank you in advance.
>
> Axplains
>
>
> --
> axplains
> ------------------------------------------------------------------------
> axplains's Profile: http://forums.techarena.in/members/axplains.htm
> View this thread: http://forums.techarena.in/server-migration/1054529.htm
>
> http://forums.techarena.in
>
>

Forgot to mention in previous post that you should backup ADMT SQL database
prior to performing the SQL repair procedure.

Jason


"Jason" wrote:

> I performed SQL repair on an ADMT server which was using SQL Express 2005 as
> follows;
>
> 1)Logon to Microsoft SQL Server Management Studio Express (download from
> Microsoft if not installed).
> 2)Select the ADMT database and put the ‘Admt’ database into emergency mode
> by running: ALTER DATABASE admt SET EMERGENCY.
> 3)Put the ‘admt’ database into single user mode like by running: ALTER
> DATABASE admt SET SINGLE_USER
> 4)Run: DBCC checkdb(admt, REPAIR_ALLOW_DATA_LOSS)
> If all goes well, you will not see any error messages and the db will be in
> a good state.
> 5)Put the ‘admt’ database back into multi-user mode so it can be used for
> production: ALTER DATABASE admt SET MULTI_USER
>
> Note: Where 'admt' is shown in the above commands replace with your ADMT
> database name if different.
>
> The above procedure should work for full SQL server product.
>
> Hope this fixes it.
>
> Jason
>
>
> "axplains" wrote:
>
> >
> > Hello,
> > I had exactly the same problem.
> >
> > Since I am not a SQLserver expert, can you please explain how to do a
> > SQL repair of the ADMT database?
> > Thank you in advance.
> >
> > Axplains
> >
> >
> > --
> > axplains
> > ------------------------------------------------------------------------
> > axplains's Profile: http://forums.techarena.in/members/axplains.htm
> > View this thread: http://forums.techarena.in/server-migration/1054529.htm
> >
> > http://forums.techarena.in
> >
> >

[axplains]

Thanks a lot, I am trying it.

I have installed the Server Management Studio Express and at execution I create a new query (right click on the DB, "New query").
When I execute "ALTER DATABASE admt SET EMERGENCY" I get the following error:

Incorrect syntax near 'emergency'

Is there anything I should do before? What am I missing?

Thanks again for you help.

Axplains

I have just tried this command in our virtual test environment which mirrors
production and it was successful. I assume your ADMT database name is called
ADMT?
You show the command within quotes for clarity I assume you did not include
the quotes in the query?

Regards,

Jason


"axplains" wrote:

>
> Thanks a lot, I am trying it.
>
> I have installed the Server Management Studio Express and at execution
> I create a new query (right click on the DB, "New query").
> When I execute "ALTER DATABASE admt SET EMERGENCY" I get the following
> error:
>
> Incorrect syntax near 'emergency'
>
> Is there anything I should do before? What am I missing?
>
> Thanks again for you help.
>
> Axplains
>
>
> --
> axplains
> ------------------------------------------------------------------------
> axplains's Profile: http://forums.techarena.in/members/axplains.htm
> View this thread: http://forums.techarena.in/server-migration/1054529.htm
>
> http://forums.techarena.in
>
>

[axplains]

Even if the command:

ALTER DATABASE admt SET EMERGENCY

went wrong, I went on (after a backup) with the other commands:

ALTER DATABASE admt SET SINGLE_USER

DBCC checkdb(admt, REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE admt SET MULTI_USER

They all worked (no error reported).
My database name is ADMT.

Unfortunately, that did not resolve the issue of "lost group membership"... maybe the "SET EMERGENCY" command is absolutely necessary?...

Thanks for your help.

I think this command may be key to the repair success. What version of SQL
are you using? the SET EMERGENCY command was not supported prior to 2005, a
less user friendly method had be performed.
--
Thanks and regards,

Jason


"axplains" wrote:

>
> Even if the command:
>
> ALTER DATABASE admt SET EMERGENCY
>
> went wrong, I went on (after a backup) with the other commands:
>
> ALTER DATABASE admt SET SINGLE_USER
>
> DBCC checkdb(admt, REPAIR_ALLOW_DATA_LOSS)
>
> ALTER DATABASE admt SET MULTI_USER
>
> They all worked (no error reported).
> My database name is ADMT.
>
> Unfortunately, that did not resolve the issue of "lost group
> membership"... maybe the "SET EMERGENCY" command is absolutely
> necessary?...
>
> Thanks for your help.
>
>
> --
> axplains
> ------------------------------------------------------------------------
> axplains's Profile: http://forums.techarena.in/members/axplains.htm
> View this thread: http://forums.techarena.in/server-migration/1054529.htm
>
> http://forums.techarena.in
>
>

[axplains]

The one included with ADMT 3.0 (I think MSDE 2005 Express)

[axplains]

Database properties say:

Microsoft SQL Server Desktop Engine
Version: 8.0.2039 SP4

And:

Microsoft SQL Server Management Studio Express Version: 9.00.2047.00

Microsoft Data Access Components (MDAC)
Version: 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)

Microsoft MSXML
Version: 2.6 3.0 4.0 6.0

[axplains]

UPDATE: database version is MSDE 2000, I downloaded and installed latest version, MSDE 2005 (but setup says the ADMT database is "blocked").
I had to remove the ADMT tool and the database files, and start it all from scratch.

I hope data will "corrupt" again... I migrate a little bunch of users at a time, and backup the database frequently (hoping it helps).