License problem

[Anonymous]

Hello,

I'm using inventor on a workstation and on a laptop. I imported it to
the laptop and it was running there.

There wasn't any problem. When I tried to restart it, I got a Windows
Box, saying "program-error, inventor stopped". It was definitely not
an error massage from inventor. I checked the license management tool.
This said, that the license was broken. Therefore I couldn't export it.
When I tried to re-import it, the tool said, that the license was
already at the laptop and is active. Therefore it could not be
re-imported.

I tried the de-install inventor, after a new installation the
situation was exactly as before. Somehow the inventor "remembered" the
broken license.

I called a dealer for assistance, he told me to uninstall both
inventor and C-Dilla, delete any of the directories and any related
entry in the registry and than to do the complete installation.
Since this, the C-Dilla doesn't start properly. Somehow the task is
running (shown in the task-manager) but when starting the inventor or
the license management tool, I get the error massage, that C-Dilla can
not be started correctly because it's not installed correctly.

I tried the patch RTS_3_27_000, but this didn't change the problem.

Could please anybody help me?

System is Win2k (German), Inventor 5.0. (German),
there was no installation done at this laptop when the error
occurred,
it is running Norton Antivirus 2003, but any of the problems that
were mentioned in this context were related to win98 (??)

I would strongly appreciate any comment,

Thanks

Andreas

--

unger @ computer.org

[Anonymous]

Anytime Inventor doesn't exit normally, it's possible that the license can
break. The solution is simply to get a new authorization code.
Re-importing can't fix a broken license; you must fix it where it is now.
Starting Inventor, it should guide you smoothly through the whole process.
Just follow the dialogs!

Uninstalling and reinstalling doesn't affect the license, which is stored in
a separate directory. (This is intentional; sometimes you need to
reinstall, but there's no reason to force reauthorization.)

Now, you must fix your installation problem before you can get a new auth
code (which you will still need). Make sure you are logged in as the local
administrator of this PC (not a network domain) for all steps.

1. Control Panel | Add/Remove Programs: uninstall C-Dilla License
Management System.
2. Reboot.
3. Reinstall the 3.27 drivers, by launching cdsetup.exe.
4. Reboot.
5. Launch Inventor. If you get an error, please say what the message and
error number are.

--Cy--


"Kunststoff- und Umwelttechnik GmbH" wrote in
message news:3F735300.5F1A6BB5@t-online.de...
> Hello,
>
> I'm using inventor on a workstation and on a laptop. I imported it to
> the laptop and it was running there.
>
> There wasn't any problem. When I tried to restart it, I got a Windows
> Box, saying "program-error, inventor stopped". It was definitely not
> an error massage from inventor. I checked the license management tool.
> This said, that the license was broken. Therefore I couldn't export it.
> When I tried to re-import it, the tool said, that the license was
> already at the laptop and is active. Therefore it could not be
> re-imported.
>
> I tried the de-install inventor, after a new installation the
> situation was exactly as before. Somehow the inventor "remembered" the
> broken license.
>
> I called a dealer for assistance, he told me to uninstall both
> inventor and C-Dilla, delete any of the directories and any related
> entry in the registry and than to do the complete installation.
> Since this, the C-Dilla doesn't start properly. Somehow the task is
> running (shown in the task-manager) but when starting the inventor or
> the license management tool, I get the error massage, that C-Dilla can
> not be started correctly because it's not installed correctly.
>
> I tried the patch RTS_3_27_000, but this didn't change the problem.
>
> Could please anybody help me?
>
> System is Win2k (German), Inventor 5.0. (German),
> there was no installation done at this laptop when the error
> occurred,
> it is running Norton Antivirus 2003, but any of the problems that
> were mentioned in this context were related to win98 (??)
>
> I would strongly appreciate any comment,
>
> Thanks
>
> Andreas
>
> --
>
> unger @ computer.org

[Anonymous]

Cy Shuster schrieb:
>
> Now, you must fix your installation problem before you can get a new auth
> code (which you will still need). Make sure you are logged in as the local
> administrator of this PC (not a network domain) for all steps.

everything re-installed, e.g. on the workstation complete uninstall
to inventor and C-Dilla,
afterwards re-installing inventor,
patch to C-Dilla (and additionally patch to the admlres.dll, required
for the German version).

for the laptop formating disk, setting up OS, same installation
procedure
as above.

(pure deinstall to C-Dilla + patch was done first, but didn't succed)

Always with reboots, between any two steps.

Result, workstation gives the message box, "an previos installation
was found, you have to re-authorize."
When saying okay, an other error-box is shown: "unexpected error
in licencing system; error code [16.1.7]"
When sayign okay, one more error box, saying: "go to dealer" and
than the inventor stops.

Result on the laptop: I've got a new auth-code (16 Bytes)

The only difference I realized, was that when installing the
C-Dilla patch, the last action on the laptop was: "do you
want to reboot". This step did not occur at the workstation.

So I could imagen, that this installation did not really succed,
because the MD is still unsing C-Dilla at this workstation?
(Because of the software running on top of the MD, I don't want
to takt any risk to loose or having to reinstall the MD.)

I could now send the auth-code to adesk, authorize the laptop
and either use the inventor only on the laptop or I could try
to export the lincence to the workstation, hoping that there
is no new trouble.

What seems to be the better idea?

Thanks for any comments,

Andreas

--

unger @ computer.org

[Anonymous]

Hi, Andreas,

Authorize on your laptop, and start using Inventor again.

You will be able to export to your workstation, but you may still have to
fix the [16.1.7] problem there. Are you sure that you have read/write
access to the directory "C:\C_DILLA"? Have you turned off any antivirus
program?

It's not a problem that it didn't ask to reboot; this is only done if
necessary. To check the installation, just start the Portable License
Utility. If it doesn't give any errors when started, then it's OK. Excuse
me, what do you mean by "MD"?

Before you export the license, make sure that the Machine ID Code hasn't
changed on either PC, because of the reformat.

--Cy--

"Andreas Unger" wrote in message
news:3F7D4D9B.CB1CDD6C@computer.org...
>
>
> Cy Shuster schrieb:
> >
> > Now, you must fix your installation problem before you can get a new
auth
> > code (which you will still need). Make sure you are logged in as the
local
> > administrator of this PC (not a network domain) for all steps.
>
> everything re-installed, e.g. on the workstation complete uninstall
> to inventor and C-Dilla,
> afterwards re-installing inventor,
> patch to C-Dilla (and additionally patch to the admlres.dll, required
> for the German version).
>
> for the laptop formating disk, setting up OS, same installation
> procedure
> as above.
>
> (pure deinstall to C-Dilla + patch was done first, but didn't succed)
>
> Always with reboots, between any two steps.
>
> Result, workstation gives the message box, "an previos installation
> was found, you have to re-authorize."
> When saying okay, an other error-box is shown: "unexpected error
> in licencing system; error code [16.1.7]"
> When sayign okay, one more error box, saying: "go to dealer" and
> than the inventor stops.
>
> Result on the laptop: I've got a new auth-code (16 Bytes)
>
> The only difference I realized, was that when installing the
> C-Dilla patch, the last action on the laptop was: "do you
> want to reboot". This step did not occur at the workstation.
>
> So I could imagen, that this installation did not really succed,
> because the MD is still unsing C-Dilla at this workstation?
> (Because of the software running on top of the MD, I don't want
> to takt any risk to loose or having to reinstall the MD.)
>
> I could now send the auth-code to adesk, authorize the laptop
> and either use the inventor only on the laptop or I could try
> to export the lincence to the workstation, hoping that there
> is no new trouble.
>
> What seems to be the better idea?
>
> Thanks for any comments,
>
> Andreas
>
> --
>
> unger @ computer.org

[Anonymous]

Cy Shuster schrieb:

> You will be able to export to your workstation, but you may still have to
> fix the [16.1.7] problem there.

any idea what this means?

>Are you sure that you have read/write
> access to the directory "C:\C_DILLA"?

yes

> Have you turned off any antivirus program?

never been running one on this machine

> To check the installation, just start the Portable License
> Utility.

sorry, I know only the German terms, does this mean the tool
to export/import the lincence?

> If it doesn't give any errors when started, then it's OK.

errors when starting it, or any errors, reported "inside" the tool?

> Excuse me, what do you mean by "MD"?

mechanical desktop.

>
> Before you export the license, make sure that the Machine ID Code hasn't
> changed on either PC, because of the reformat.

if it would have changed, removing and creating the machines in the
pool is the right anwser?

Thanks Andreas

[Anonymous]

"Kunststoff- und Umwelttechnik GmbH" wrote in
message news:3F7D8A9E.EFC0A066@computer.org...
>
> Cy Shuster schrieb:
>
> > You will be able to export to your workstation, but you may still have
to
> > fix the [16.1.7] problem there.
>
> any idea what this means?

Yes, at startup it's either a permissions problem writing to the license
directory (C:\C_DILLA), or a corrupt license. Since you've reformatted,
it's the first problem (no license left).

> >Are you sure that you have read/write
> > access to the directory "C:\C_DILLA"?
>
> yes
>
> > Have you turned off any antivirus program?
>
> never been running one on this machine
>
> > To check the installation, just start the Portable License
> > Utility.
>
> sorry, I know only the German terms, does this mean the tool
> to export/import the lincence?

Yes.

> > If it doesn't give any errors when started, then it's OK.
>
> errors when starting it, or any errors, reported "inside" the tool?

At startup. If the installation is bad, you'll get errors right away.

> > Excuse me, what do you mean by "MD"?
>
> mechanical desktop.

Danke! Auf Englisch, we usually say "MDT".

> >
> > Before you export the license, make sure that the Machine ID Code hasn't
> > changed on either PC, because of the reformat.
>
> if it would have changed, removing and creating the machines in the
> pool is the right anwser?

Yes, that's all. If you export to the wrong ID code, there's no way to get
the license back (like emailing to the wrong address!).

--Cy--

[Anonymous]

Cy Shuster wrote:

> > > You will be able to export to your workstation, but you may still have
> to
> > > fix the [16.1.7] problem there.
> >
> > any idea what this means?
>
> Yes, at startup it's either a permissions problem writing to the license
> directory (C:\C_DILLA), or a corrupt license. Since you've reformatted,
> it's the first problem (no license left).

no, I haven't reformat the machine that reports this error code.
(It was the other one I reformated.) But it's likely that I corruped
the licence.
The question I'm wondering about is, if I'll export the licence
to this machine (assume correct machine IDs), will this fix the
corrupt licence, or will this bring me in the same situation,
that I have the licence exported to a machine, that has a problem?

> > > To check the installation, just start the Portable License
> > > Utility.
> > > If it doesn't give any errors when started, then it's OK.

I dont get any errors, when starting this tool.

> > > Excuse me, what do you mean by "MD"?
> >
> Danke! Auf Englisch, we usually say "MDT".

sorry, my fault.

Thanks,

Andreas

--

unger @ computer.org