VAult 2014 File Migration error. Servicemodule.exe has stopped working

[Lalitkmr123]

Hi,
I just upgraded our Autodesk vault from 2013 to 2014 version along with Autodesk Inventor product design suite.

Now I am in the process of migrating the files to 2014 version.

I am following the sequence of migrating as follows:

ipt-iam-ipn-idw.

I do this through Task Scheduler.

I have done this in past where I will create a sequential Task wherein I will first migrate ".ipt" files then "Iam" then "ipn" and finally "idw" files for each design folders.

When i am doing this for 2014, the process stopped in between with an error "Servicemodule.exe has stopped working".

Can Anyone tell me what might be the problem. I am attaching the screen shot and logfiles from the Task scheduler

Any Help is appreciated.

Regards

Lalit

[JeffPaquette6500]

Try disabling UAC: http://help.autodesk.com/cloudhelp/2014/ENU/Vault/files/GUID-CC794B3F-9DCE-4CDC-89DB-D2E341E26936.ht...

If anti-virus is running, try turning that off completely.

Also check Windows Event logs, System and/or Application might give some insight to the error.

[Lalitkmr123]

Jeff,

Thanks for your reply. I tried following actions as per your instructions.

1. I turned off our antivirus completely. Then I started the sequential
task of migrating iam--> ipn---> Idw. As earlier, it went through checking
out files for iam migraion--- migrate--check in. The error showed up after
it completed check-in of iam files after migration and it started file
checkout for ipn files or second section of the sequential task: .

2. I changed User account Control Settings to "Never notify" on my work
station (Client, Windows 7). rebooted.
I checked UAC setting on vault server (Windows server 2008R2). They are
at "never notify" already.
Turned off antivirus.
Then I started the same sequential task of migrating as mentioned in
step 1.
The error notice came at the same point e.g. after completing 1st section
(iam) and after starting second section (ipn).

I am attaching the screen shot of the error and task scheduler log file.

Also I copied the problem signature details from the dialog box which i am
pasting below.


"Problem signature:
Problem Event Name: BEX64
Application Name: ServiceModule.exe
Application Version: 18.1.22200.0
Application Timestamp: 5238c002
Fault Module Name: StackHash_c30d
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000034607f0
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: c30d
Additional Information 2: c30d0f95bf9f5f217366af85e9c351d8
Additional Information 3: 3fcc
Additional Information 4: 3fcce9d1e7373832fdc058c0819f2c9b

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy
statement offline:
C:\Windows\system32\en-US\erofflps.txt.
"

3. I was able to get to windows event log , but don't know what to look
for. if you tell me what information to look for or how to export the log
so that you can see it, please let me know how.


I must also note that this error occurs only when I am scheduling the
"Sequential task". When I am doing only one migration task (Say Migrating
"Iam" files only) i don't encounter any problem. in fact that's how I had
to to do migration of all the files types.

Regards

Lalit

[JeffPaquette6500]

In event viewer, look for the servicemodule.exe error. Perhaps there is another error/event that causes it.

To save the event logs:

In Event Viewer, expand Windows Logs.

• Application, Right mouse Click, Save All Events As
• System, Right mouse Click, Save All Events As

[Lalitkmr123]

Jeff,

I ran the sequential task again as per your instruction on 1.13 pm. and the
error came at around 1.17 pm after completing migration of first type (iam)
and starting checkout of second type (ipn).

These logs were extracted as per the instructions in your last email.
The size of the log files is quite big so I am sending them to you through
my google drive. If this does not work then I will send you the screen
captures
APPLICATION LOG.evtx

SYSTEM LOG.evtx


Regards

Lalit

PS: I ran the same sequential task at around 11.46 am today morning. It
gave me the same error, however the antivirus was active on my workstation
at that time. This explains the presence of another error event at 11.49 am
today in the logs attached.

[JeffPaquette6500]

Lalit,

I cannot access Google drive, so if this is still an issue, the next best step is to open a support case. Task Scheduler is a feature of Inventor, so please open the case with the product as Inventor. Thanks.

[kmecke]

Hi there -

sorry for digging out this thread, but I am running exactly into the same error with IV 2015 SP1.

Whats the end of the story???

Curiously - Best regards

Kai

[ErhardKlamminger]

Hello Lalitkmr123

Your post was done for some years, but maybe I have the answer now why your migration fails all the time.

In my case I am currently updating our standard parts from 2018 to 2020 file version (over 100000 parts) and I had the same issue. Reason is, that if you use more CPUs, it always crashes. So change to only one CPU and it runs through without any crash anymore.

So the migration can not work with multi CPU. Autodesk should rework this behavior. I don´t know why this setting is available, but it does not work. I will try if more CPUs are working, when I start the checkin into Vault with Task Scheduler.

Hopefully this helps for future migrations with Task Scheduler.

BR Hatl