- Deleted by N/A
I am posting this here first, as you are our customers.
I will then be posting this in the developers forums as this is utter nonsense!
Posft added a new DLL called:
Services.CFMX.dll
this was in addition to one before, we fully disabled this DLL and also manually updated the status xml file that this dll checks to see if it needs to update the DSNs(err I mean fully corrupt them!)
The prior DLL is still in existance, but both had to be disabled, it was:
Resources.IIS.ColdFusion.dll
the xml file that was read was as such:
<status>
<DSNUpdated>false</DSNUpdated>
</status>
Which I manually changed to:
<status>
<DSNUpdated>true</DSNUpdated>
</status>
Then set to read-only so it would always think the DSNs have been updated.
If you have a domain on Win6, and need to enable a domain for Coldfusion, please submit a ticket, we will do this manually. After the problems caused with CF and Hsphere I will not be allowing it to edit configs until I know it is working properly.
I will then be posting this in the developers forums as this is utter nonsense!
Posft added a new DLL called:
Services.CFMX.dll
this was in addition to one before, we fully disabled this DLL and also manually updated the status xml file that this dll checks to see if it needs to update the DSNs(err I mean fully corrupt them!)
The prior DLL is still in existance, but both had to be disabled, it was:
Resources.IIS.ColdFusion.dll
the xml file that was read was as such:
<status>
<DSNUpdated>false</DSNUpdated>
</status>
Which I manually changed to:
<status>
<DSNUpdated>true</DSNUpdated>
</status>
Then set to read-only so it would always think the DSNs have been updated.
If you have a domain on Win6, and need to enable a domain for Coldfusion, please submit a ticket, we will do this manually. After the problems caused with CF and Hsphere I will not be allowing it to edit configs until I know it is working properly.