WebSite X5Help Center

 
Dave K.
Dave K.
User

C# command line error, license activation loop  en

Autor: Dave K.
Visitado 2740, Seguidores 1, Compartilhado 0  

I installed V9 on my laptop, and keep getting "C# command line error" when starting V9. Keeps going into reactivation loop even though when I plug in the license number, it says it was successfully activated. Any ideas?  Sealed

Publicado em
10 RESPOSTAS - 1 CORRIGIR
Dave K.
Dave K.
User
Autor

Hello Claudio - I have not. I tried searching the support site several times and didn't see this one come up at all. I will give it a try and check back after I'm done. Cool

Ler mais
Publicado em de Dave K.
Dave K.
Dave K.
User
Autor

Hello Claudio,

I tried the suggested procedure - including removing NET 4.0 first. However, NET3.5 doesn't want to install on my system for some reason. I've tried several times, to no avail. I am curious though - I've got V9 working fine on my desktop tower and only have NET 4.0 installed on it and there are no issues. Any suggestions? Frown

Ler mais
Publicado em de Dave K.
Incomedia
Claudio N.
Incomedia
However, NET3.5 doesn't want to install on my system for some reason

Does it show an error message?

Ler mais
Publicado em de Claudio N.
Dave K.
Dave K.
User
Autor

Hello Claudio;

   I didi some research with Microsoft, and I understand now why I didn't see NET3.5 in the program list. Windows 7 has NET3.5, 3.0, 2.0 etc. embedded in the operating system so they are no longer add-on packages. Only 4.0 and 4.5 are. For 3.5, one only has to go in and trun on the 3.5 features (which I did), and still have teh same problem. The error that comes up first is the "Visual C# Comand Line error" pop up window, and the error attempts to seek a solution on the internet. If I close it, the activation loop starts again. It would appear that the error lies in the C# command compiler somewhere. I've done a remove of NET4.0 and a repair. I seem to recall that I had to request some kind of activation code the last time I did this with Version 8. Is that the case here? I've enclosed a jpg of the error I get after I plug int he license code, etc.

Dave

Ler mais
Publicado em de Dave K.
Incomedia
Claudio N.
Incomedia

Hi Dave,

You're right, Windows 7 comes with .NET 3.5 preinstalled. Anyway, I've found that installing/deleting new software on a pc can corrupt .NET.

There's a .NET cleaning tool which can reset your .NET framework installation. Use it to remove all your .NET installations. You can download it from here:http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

Then reinstall .NET 3.5 from here:http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=22

If it doesn't work, use the .NET Verification Tool to get more informations about the problem and send me the logs:http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

Thank you!

Ler mais
Publicado em de Claudio N.
Dave K.
Dave K.
User
Autor

Claudio - I've been reading the astebner blog, but this process won't work since 3.5 is built into the OS. Matter of fact, his blog specifically indicates that - quoted here: ("One important note – as indicated above, the cleanup tool will not allow you to remove a version of the .NET Framework that is installed as part of the OS it is running on. " ).  On that premise alone, a 3.5 install won't work in Windows 7 ... it's built in.

So, the only one it will clean and remove is V4.0. I've already removed 4.0 and used the verification tool and it comes up clean.  

What about the Visual C# error? Is that related to the activation loop? I've looked through the blogs about this and no one else who's run into the activation issue seems to have that problem.

I don't want to have to go back to V8 on this one. I'd prefer to get V9 running if possible. I've checked the install list on both ny desktop and laptop, and can't find anything unusual - yet my desktop allows to install V9 and activate it with no issues.  

Ler mais
Publicado em de Dave K.
Dave K.
Dave K.
User
Autor

I will check it out and get back to you...

Ler mais
Publicado em de Dave K.
Dave K.
Dave K.
User
Autor

Claudio - I was finally able to get it installed and activated. The solution for me was to run chkdsk. The SFC scanner wouldn't work on my system, would only get to about 84%. Looks like some corruption in a few files - chkdsk took care of it. You can close out this one, I'm all set now.

Thank you for your assistance - much appreciated. Laughing

Ler mais
Publicado em de Dave K.