Skip navigation
lukN
Currently Being Moderated

ColdFusion 8: .NET integration issue

Jan 9, 2009 3:49 AM

I have problem with ColdFusion .NET integration.
I installed CF 8 server on my computer (Windows Vista, CF8 Version 8,0,1,195765, .NET Framework 3.5 SP1, server: C:/ColdFusion8/, sites: C:/ColdFusiion8/wwwroot). All was OK and the test script was working fine.
I copyed this file on server (Windows Server 2003 Standard Edition SP2, CF8 Version 8,0,1,195765, server: C:/ColdFusion8/, sites: D:/wwwroot) and installed .NET framework 3.5 SP1 and ColdFusion .NET integration service........
I am getting the below error:

Class System.IO.DriveInfo not found in the specified assembly list.
The assembly that contains the class must be provided to the assembly attribute.

I can't configure Windows Server. Please do provide a solution for this
 
Replies
  • Currently Being Moderated
    Jan 9, 2009 6:12 AM   in reply to lukN
    What are the contents of "this file" and its dependencies?
     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2009 8:06 AM   in reply to lukN
    Some things to check or try

    1. Permissions, verify that the account the ColdFusion services run as have permissions to the files and directories containing the .NET framework.

    2. Paths. I notice that your production server has web code on a different drive. You might try using the assembly attribute of cfobject to specify the full path to the DriveInfo class. I realize that since it is part of the global assembly cache this shouldn't be required, but I would try it.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 2, 2010 8:28 AM   in reply to lukN

    When you installed the .NET framework on the new server, was there already an earlier version of the .NET framework on the server? Also did you install the CF/.NET integration service before or after installing .NET v. 3.5? I ran into this problem before on a server that had the .NET integration service installed and .NET framework v 2.0...upgrading the .NET version to 3.5 caused the problem, since the ColdFusion .NET integration service had configured itself to use the earlier version of the .NET framework. Uninstalling and then reinstalling ColdFusion .NET integration service fixed the problem in my case.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points