File Server Migration Toolkit (FSMT 1.1): Fatal Error

Hi,
I've to use the FSMT to migrate 2 File Server (MS Windows 2000) in a new one
Cluster (MS Windows Server 2003); the OSs languages are Italian.

I don't have to consolidate the DFS Root, so I won't run the DFS
Consolidation Root Wizard.
After the FSMT setup on the new Cluster, I receive the following Fatal Error
in any case, also when the source server is a test File Server not in a DFS
structure.

It seems to be a common problem, but without particular solution or
workaround...
I've already tried to delete\create the network name, disable the File\Print
Services on the HeartBeat netcard... but without success!

Could you help me please?

Thanks in advance
Francesco

------------------
A fatal error has occurred please contact Microsoft Technical Support with
the following information:

Riferimento a un oggetto non impostato su un'istanza di oggetto.

Stack Trace:
in FSMigration.Validator.ValidateExistingTargetShareC onlict(ShareBase share)
in FSMigration.Validator.ValidateSingleShare(ShareBas e share)
in FSMigration.Validator.ValidateShare(ShareBase share)
in FSMigration.Validator.ValidateServer(SourceServer server)
in FSMigration.Validator.Run()
in FSMigration.ValidationWorkItem.PreProcessServer(So urceServer server)
in FSMigration.ThreadController.EnsureServerPreProces sed(SourceServer
server)
in FSMigration.ThreadController.ThreadProc(ThreadWrap per thisThread,
SourceServer initialServer)
in FSMigration.ThreadWrapper.ThreadProc()
in System.Threading.ThreadHelper.ThreadStart_Context( Object state)
in System.Threading.ExecutionContext.Run(ExecutionCon text executionContext,
ContextCallback callback, Object state)
in System.Threading.ThreadHelper.ThreadStart()
------------------

If someone were interested, I've solved myself the issue using the previous
version (1.0); that version continues to work great on cluster MSCS win2003
without any fatal error!
The MS Support confirms to me the problem should be caused by a sw bug of
the 1.1.

Regards,
Francesco


"Francesco" wrote:

> Hi,
> I've to use the FSMT to migrate 2 File Server (MS Windows 2000) in a new one
> Cluster (MS Windows Server 2003); the OSs languages are Italian.
>
> I don't have to consolidate the DFS Root, so I won't run the DFS
> Consolidation Root Wizard.
> After the FSMT setup on the new Cluster, I receive the following Fatal Error
> in any case, also when the source server is a test File Server not in a DFS
> structure.
>
> It seems to be a common problem, but without particular solution or
> workaround...
> I've already tried to delete\create the network name, disable the File\Print
> Services on the HeartBeat netcard... but without success!
>
> Could you help me please?
>
> Thanks in advance
> Francesco
>
> ------------------
> A fatal error has occurred please contact Microsoft Technical Support with
> the following information:
>
> Riferimento a un oggetto non impostato su un'istanza di oggetto.
>
> Stack Trace:
> in FSMigration.Validator.ValidateExistingTargetShareC onlict(ShareBase share)
> in FSMigration.Validator.ValidateSingleShare(ShareBas e share)
> in FSMigration.Validator.ValidateShare(ShareBase share)
> in FSMigration.Validator.ValidateServer(SourceServer server)
> in FSMigration.Validator.Run()
> in FSMigration.ValidationWorkItem.PreProcessServer(So urceServer server)
> in FSMigration.ThreadController.EnsureServerPreProces sed(SourceServer
> server)
> in FSMigration.ThreadController.ThreadProc(ThreadWrap per thisThread,
> SourceServer initialServer)
> in FSMigration.ThreadWrapper.ThreadProc()
> in System.Threading.ThreadHelper.ThreadStart_Context( Object state)
> in System.Threading.ExecutionContext.Run(ExecutionCon text executionContext,
> ContextCallback callback, Object state)
> in System.Threading.ThreadHelper.ThreadStart()
> ------------------
>

Hi ,

Would u happen to have a link to the old 1.0? Im having the exact same
problem

Rgds,

M.

"Francesco" wrote:

> If someone were interested, I've solved myself the issue using the previous
> version (1.0); that version continues to work great on cluster MSCS win2003
> without any fatal error!
> The MS Support confirms to me the problem should be caused by a sw bug of
> the 1.1.
>
> Regards,
> Francesco
>
>
> "Francesco" wrote:
>
> > Hi,
> > I've to use the FSMT to migrate 2 File Server (MS Windows 2000) in a new one
> > Cluster (MS Windows Server 2003); the OSs languages are Italian.
> >
> > I don't have to consolidate the DFS Root, so I won't run the DFS
> > Consolidation Root Wizard.
> > After the FSMT setup on the new Cluster, I receive the following Fatal Error
> > in any case, also when the source server is a test File Server not in a DFS
> > structure.
> >
> > It seems to be a common problem, but without particular solution or
> > workaround...
> > I've already tried to delete\create the network name, disable the File\Print
> > Services on the HeartBeat netcard... but without success!
> >
> > Could you help me please?
> >
> > Thanks in advance
> > Francesco
> >
> > ------------------
> > A fatal error has occurred please contact Microsoft Technical Support with
> > the following information:
> >
> > Riferimento a un oggetto non impostato su un'istanza di oggetto.
> >
> > Stack Trace:
> > in FSMigration.Validator.ValidateExistingTargetShareC onlict(ShareBase share)
> > in FSMigration.Validator.ValidateSingleShare(ShareBas e share)
> > in FSMigration.Validator.ValidateShare(ShareBase share)
> > in FSMigration.Validator.ValidateServer(SourceServer server)
> > in FSMigration.Validator.Run()
> > in FSMigration.ValidationWorkItem.PreProcessServer(So urceServer server)
> > in FSMigration.ThreadController.EnsureServerPreProces sed(SourceServer
> > server)
> > in FSMigration.ThreadController.ThreadProc(ThreadWrap per thisThread,
> > SourceServer initialServer)
> > in FSMigration.ThreadWrapper.ThreadProc()
> > in System.Threading.ThreadHelper.ThreadStart_Context( Object state)
> > in System.Threading.ExecutionContext.Run(ExecutionCon text executionContext,
> > ContextCallback callback, Object state)
> > in System.Threading.ThreadHelper.ThreadStart()
> > ------------------
> >

Hi,
unfortunately on MS\downloads you'll get only the last one 1.1... I've found
it on my pers store for a previous and old download.

Anyway, try on this sw website archive:
http://www.xcopy32.com/details.php?file=257

Regards


"Mino" wrote:

> Hi ,
>
> Would u happen to have a link to the old 1.0? Im having the exact same
> problem
>
> Rgds,
>
> M.
>
> "Francesco" wrote:
>
> > If someone were interested, I've solved myself the issue using the previous
> > version (1.0); that version continues to work great on cluster MSCS win2003
> > without any fatal error!
> > The MS Support confirms to me the problem should be caused by a sw bug of
> > the 1.1.
> >
> > Regards,
> > Francesco
> >
> >
> > "Francesco" wrote:
> >
> > > Hi,
> > > I've to use the FSMT to migrate 2 File Server (MS Windows 2000) in a new one
> > > Cluster (MS Windows Server 2003); the OSs languages are Italian.
> > >
> > > I don't have to consolidate the DFS Root, so I won't run the DFS
> > > Consolidation Root Wizard.
> > > After the FSMT setup on the new Cluster, I receive the following Fatal Error
> > > in any case, also when the source server is a test File Server not in a DFS
> > > structure.
> > >
> > > It seems to be a common problem, but without particular solution or
> > > workaround...
> > > I've already tried to delete\create the network name, disable the File\Print
> > > Services on the HeartBeat netcard... but without success!
> > >
> > > Could you help me please?
> > >
> > > Thanks in advance
> > > Francesco
> > >
> > > ------------------
> > > A fatal error has occurred please contact Microsoft Technical Support with
> > > the following information:
> > >
> > > Riferimento a un oggetto non impostato su un'istanza di oggetto.
> > >
> > > Stack Trace:
> > > in FSMigration.Validator.ValidateExistingTargetShareC onlict(ShareBase share)
> > > in FSMigration.Validator.ValidateSingleShare(ShareBas e share)
> > > in FSMigration.Validator.ValidateShare(ShareBase share)
> > > in FSMigration.Validator.ValidateServer(SourceServer server)
> > > in FSMigration.Validator.Run()
> > > in FSMigration.ValidationWorkItem.PreProcessServer(So urceServer server)
> > > in FSMigration.ThreadController.EnsureServerPreProces sed(SourceServer
> > > server)
> > > in FSMigration.ThreadController.ThreadProc(ThreadWrap per thisThread,
> > > SourceServer initialServer)
> > > in FSMigration.ThreadWrapper.ThreadProc()
> > > in System.Threading.ThreadHelper.ThreadStart_Context( Object state)
> > > in System.Threading.ExecutionContext.Run(ExecutionCon text executionContext,
> > > ContextCallback callback, Object state)
> > > in System.Threading.ThreadHelper.ThreadStart()
> > > ------------------
> > >

You're a lifesaver

This one works like charm.

Thx & Rgds,



"Francesco" wrote:

> Hi,
> unfortunately on MS\downloads you'll get only the last one 1.1... I've found
> it on my pers store for a previous and old download.
>
> Anyway, try on this sw website archive:
> http://www.xcopy32.com/details.php?file=257
>
> Regards
>
>
> "Mino" wrote:
>
> > Hi ,
> >
> > Would u happen to have a link to the old 1.0? Im having the exact same
> > problem
> >
> > Rgds,
> >
> > M.
> >
> > "Francesco" wrote:
> >
> > > If someone were interested, I've solved myself the issue using the previous
> > > version (1.0); that version continues to work great on cluster MSCS win2003
> > > without any fatal error!
> > > The MS Support confirms to me the problem should be caused by a sw bug of
> > > the 1.1.
> > >
> > > Regards,
> > > Francesco
> > >
> > >
> > > "Francesco" wrote:
> > >
> > > > Hi,
> > > > I've to use the FSMT to migrate 2 File Server (MS Windows 2000) in a new one
> > > > Cluster (MS Windows Server 2003); the OSs languages are Italian.
> > > >
> > > > I don't have to consolidate the DFS Root, so I won't run the DFS
> > > > Consolidation Root Wizard.
> > > > After the FSMT setup on the new Cluster, I receive the following Fatal Error
> > > > in any case, also when the source server is a test File Server not in a DFS
> > > > structure.
> > > >
> > > > It seems to be a common problem, but without particular solution or
> > > > workaround...
> > > > I've already tried to delete\create the network name, disable the File\Print
> > > > Services on the HeartBeat netcard... but without success!
> > > >
> > > > Could you help me please?
> > > >
> > > > Thanks in advance
> > > > Francesco
> > > >
> > > > ------------------
> > > > A fatal error has occurred please contact Microsoft Technical Support with
> > > > the following information:
> > > >
> > > > Riferimento a un oggetto non impostato su un'istanza di oggetto.
> > > >
> > > > Stack Trace:
> > > > in FSMigration.Validator.ValidateExistingTargetShareC onlict(ShareBase share)
> > > > in FSMigration.Validator.ValidateSingleShare(ShareBas e share)
> > > > in FSMigration.Validator.ValidateShare(ShareBase share)
> > > > in FSMigration.Validator.ValidateServer(SourceServer server)
> > > > in FSMigration.Validator.Run()
> > > > in FSMigration.ValidationWorkItem.PreProcessServer(So urceServer server)
> > > > in FSMigration.ThreadController.EnsureServerPreProces sed(SourceServer
> > > > server)
> > > > in FSMigration.ThreadController.ThreadProc(ThreadWrap per thisThread,
> > > > SourceServer initialServer)
> > > > in FSMigration.ThreadWrapper.ThreadProc()
> > > > in System.Threading.ThreadHelper.ThreadStart_Context( Object state)
> > > > in System.Threading.ExecutionContext.Run(ExecutionCon text executionContext,
> > > > ContextCallback callback, Object state)
> > > > in System.Threading.ThreadHelper.ThreadStart()
> > > > ------------------
> > > >