CLR assembly DLL file location? Corrupted

  • CLR file location.

    Is it C:\windows\Framework\version?

    Frequently facing problems SSIS - backup package dll files are corrupted and maintenance plan not taken automatically backups as per schedule.

    Is it CLR can access windows level DLL files other than DotNet Framework files? POPUP error messages display after login the server as below

    1. DotNet framework Initialization Error – mscorwks.dll could not loaded

    2. Runtime error – Microsoft Visual C ++ Runtime library

    3. Launchupdater.exe fatal error unable to load Jit compiler (mscorjit.dll) file may be missing or corrupted

    4. Error – LicenseManRes.dll could not be found (AV).

    Does 4 popup error msg may be SQL CLR can lead to affected these DLL files? Pls. confirm.

    thanks

    ananda

  • Frequently facing problems SSIS - backup package dll files are corrupted and maintenance plan not taken automatically backups as per schedule.

    Are you backing up SSIS packages thought he CLR dll?

    Is it CLR can access windows level DLL files other than DotNet Framework files? POPUP error messages display after login the server as below

    you can get this information from a .net developer.

    Regards
    Durai Nagarajan

  • i have verified the which database has using CLR objects, there two type of CLR stored prcedure and CLR Scalar funtion. but these two objects CLR Permission is UNSAFE_ACCESS. it is unrestricted access to resources both SQL server and windows level.

    How can i modified the SAFE access the most restrictive permission set. Code executed by an assembly with SAFE permissions cannot access external system resources such as files, the network, environment variables, or the registry. (change access can be done by developer? or DBA can do that).

    Thanks

    ananda

  • This link may be useful for you

    http://www.codeproject.com/Articles/19954/Execute-NET-Code-under-SQL-Server-2005

    Regards
    Durai Nagarajan

  • I checked that article, it should be UNSAFE Access in CLR object then only external resource will be used, so SAFE access not possible to set the CLR object.. But i hope EXTERNAL accress will be possible to avoid the corruption .Net related dlls files. so i ask them development team to change EXTERNAL access will test it.

    Thanks

    ananda

  • I don't know much about it but our development team asked DBA's to run long back so i remembered it.

    Regards
    Durai Nagarajan

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply