Using InstallAware 7 on Windows 2000 Terminal Server

casic · Post by **casic** » Wed Oct 24, 2007 4:03 am

Hi there,

we would like to use InstallAware 7 on a Windows 2000 Terminal Server. Everything works except .NET 2.0 assemblies. When building a setup with .NET 2.0 assemblies this error occurs:

Error during build: Unable to get assembly information for K:\\Assemblies\\NET 2.0\\KSR C1Reports Wrapper\\C1.C1Preview.2.dll

.NET Framework 2.0 is installed on Terminal Server. On a local XP machine there are no problems. Are there any restrictions to a Windows 2000 Terminal Server? Using InstallAware 7 Studio Admin Trial.

Thanks for the info,

Markus

Alex_Ronquillo · Post by **Alex_Ronquillo** » Wed Oct 24, 2007 10:32 am

Not that we know Markus. Make sure the .NET 2.0 is correctly installed in the 2000 Terminal Server.

casic · Post by **casic** » Wed Oct 31, 2007 5:24 am

Hi,

sorry to tell you that I tried 3 different Windows 2000 Server installations (also on a complete new installation with all service packs and patches). On all installations I have the same problem that the assembly information couldn't be retrieved. Can you give me a hint please which tool (I think IA7 is using an external tool) is used to retrieve the assembly information so I could check it?

Thank you very much,

Markus

Gizm0 · Post by **Gizm0** » Wed Oct 31, 2007 6:40 am

Terminal Server 2000 had some strange behaviors occuring from Permissions issues. Check if the target directory has permissions to be access by the Terminal User group, and the default terminal user.

If this is not the case, contact again. Sorry for the trouble though.

casic · Post by **casic** » Wed Oct 31, 2007 9:02 am

Hi,

I have admin rights so there should be no problem with copying files. The setup contains about 500 files and only 3 assemblies. All work fine except these three assemblies (if I exclude these 3 assemblies I get a full build).

Very strange...

cu

Markus

Gizm0 · Post by **Gizm0** » Wed Oct 31, 2007 9:22 am

Maybe the assemblies have some kind of protection from business objects when detecting the run under terminal services?

For licensing purposes it might be locked not to run under Terminal Services. Have you checked that case?

casic · Post by **casic** » Fri Nov 02, 2007 9:25 am

Hi,

you are absolutly right: it was a license issue of one .NET library which is used in our assemblies. As soon as this license issue was solved, the build completes successfully

Thank you very much for your support,

Markus

Gizm0 · Post by **Gizm0** » Fri Nov 02, 2007 8:03 pm

That's Great! Glad i helped!