Then you need to follow these steps to properly set up an MS Access 32 bit Data Source on a 64 bit ColdFusion 10 installation running on Windows 2008 SP2 (because the add new data source function in ColdFusion 10 Admin doesn’t do correctly):

Preparations

Set up the 32 bit System DSN

Create the Data Source in ColdFusion Administrator

Verify Connection to Data Source

1 Preparations

Before we get started, here are some tips to ensure a successful setup:

If the Microsoft Access driver is not available, then please download and install it:

Copy this file to the server where ColdFusion is installed: AccessDatabaseEngine_x64.exe

Like this:

Let’s say we are performing a system maintenance task on the database server but not the web server will not be affected. Given that our websites are database-driven and use this database server, we want to redirect all website visits to a maintenance page during the system maintenance period.

Here are the steps:

Create the site maintenance page

Create a redirect rule using the IIS URL Rewrite

Activate the rule at system maintenance time

Create the site maintenance page

1 Create an HTML page with the following information

Page title

Brief description of maintenance window

Time service resumes

Include the style inline on the page, and save this page as maintenance.html on the website root. Here’s a sample:

2 Creating the IIS URL Rewrite Redirect Rule

Let’s use the IIS Rewrite Module to create a rule to redirect all requests to the website to a maintenance page that we created in the step above:

Logon to the IIS Manager

Select the site and then URL Rewrite

Add Rule(s)…

Blank Rule under Inbound Rules

Enter the following for this new rule:

Name: Site Maintenance

Expand the Match URL section and enter or select the following:

Requested URL: Matches the pattern

Using: Regular Expressions

Pattern: (.*)We want to match all requests coming to the site, hence (.*)

Like this:

After upgrading to ColdFusion 11, verifying a data source in ColdFusion Admin (especially those where you need to specify the instance name as part of the server, i.e. Server: server-name/instance-name) will result in the following error thrown:

Connection verification failed for data source: <data-source-name>java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Conflicting connection information. When the instance name is specified, it is invalid to specify the port number.

The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Conflicting connection information. When the instance name is specified, it is invalid to specify the port number.

Follow these steps to resolve the above error:

Edit the data source

Expand Show Advanced Settings

In the Connection String box, enter: allowPortWithNamedInstance=true

Click Submit

You should now see the message: data source updated successfully

Repeat the above steps for all data sources with the same entry for its Server, i.e. those with values of server-name/instance-name.

Like this:

Upgrading to ColdFusion 11 from 10, on the same machine where ColdFusion 10 exists, is simple and error-free with careful planning. Here are the steps on how to successfully upgrade to Adobe ColdFusion 11 from 10:

Download ColdFusion 11 from Adobe (need to sign to Adobe, sign up first if this is your first time)

Run as administratorColdFusion_11_WWEJ_win64.exe to kick off the ColdFusion 11 installer.

Follow the installation wizard to complete the first stage of the installation

Launch the Configuration Wizard to complete the second stage of the installation

Environment

Windows 7 Professional (should also work on Windows 2008) 64 bit

Existing install of ColdFusion 10

IIS web server

Windows Features

Before you launch the ColdFusion installer, please ensure you turn on the following Windows features (in particular the Application Development features):

Here are some screenshots of the above selections from Windows Server 2012 R2:

Installation Steps

Here are the screenshots from the stage one installation wizard:

Enter the serial number if you have one or later after the install. You can also select the 30-day trial as indicated above. After 30 days, it will revert to the Developer Edition if you don’t enter a serial number.

Development Profile:Use this profile only for development purposes. Note that features like Server Debugging and RDS are enabled by default for this profile.

Production Profile:Use this profile for production purposes. All debug features and RDS are disabled for this profile.

Production Profile + Secure Profile:Use this profile for a highly-secure production deployment that will allow a more fine-grained secure environment. For details, see the secure profile guide (http://www.adobe.com/go/cf11_secureprofile).

Allowed admin IPs are the client IP addresses that can access the ColdFusion administrator. They can be a comma separated list of IP addresses (for example, 11.181.28.54, 11.180.26.32, etc.). IP addresses can range from 10-30, or * wild cards. Both IPv4 and IPv6 addresses are supported.

I know the screenshot indicates All IIS websites was selected. However if you are installing on a server where you have an existing ColdFusion 10 installation, it is best to select Configure specific IIS website or another web server. Then click Add to create a connection for a temporary IIS website for ColdFusion 11. So prior to installation, please ensure you setup a temporary IIS website for this purpose. It can be removed afterward.

If you have an existing ColdFusion 10 installation, and selected All IIS websites or a specific IIS website which is currently configure to connect to ColdFusion 10, it will failed at the Configuration Wizard step (stage two of the installation) with an error similar to this:

The above error assume you selected Default Web Site as the specific website to connect for ColdFusion 11. This Default Web Site is also currently connected to ColdFusion 10. So either disconnect it from ColdFusion 10 first or just create a temporary IIS website to use for connecting to ColdFusion 11.

Enter a strong password for the administrator. The requirements are:

at least 8 characters

1 letter in upper case

1 letter in lower case

1 numeric

1 special character

Launch the wizard and log in as the administrator to complete the configuration. In ColdFusion 11, there an option to import configurations from ColdFusion 10 if you’re installing on the same server machine. This step can be skipped if you like, but you will need to deploy the ColdFusion archives to restore the configurations you have saved after the configuration wizard completes successfully.

If you’ve made this far, then congratulations! You’ve successfully installed ColdFusion 11 on the server.

To complete the upgrade and transfer all website to ColdFusion 11, you will need to use the Web Configuration Tool to remove ColdFusion 10 connections and then add the new ColdFusion 11 connections.

Remember, if you create ColdFusion instances, you will need to run the Web Configuration Tool from their respective location, i.e. launch as administrator wsconfig.exe from <instance-name>/runtime/bin/wsconfig.exe.

Once the connections are all done, browse your website and ensure that it is working as expected.

Like this:

I am performing routine checks of the SharePoint 2010 server logs, and see many of these event ID 10016 DistributedCOM error messages in the Windows System log and wonder what could be causing them. Checking the Application log and I also see MsiInstaller warning messages at around the same time related to SharePoint 2010.

The error message for event ID 10016:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {000C101C-0000-0000-C000-000000000046} to the user domain\sp-farm-account SID (guid) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Here’s a screen grab of the error from the System log:

After a bit of research online, it turns out that the SharePoint 2010 Product Version Job runs at 12.45am every day. And at precisely that time every day, there were MsiInstaller warnings in the Application log and errors in the System log (event ID 10016).

So from what I have read online, here are the steps to resolve the event 10016 error that relates to distributedCOM:

On the server where the above error occur, click Start > Run > type regedit to acess the registry

Copy the GUID from System log General tab, i.e. 000C101C-0000-0000-C000-000000000046

In the registry editor, click to select the top most branch of the registry – Computer

From the menu, Edit > Find, paste in the GUID. It’ll stop at the application entry, i.e. AppID sub-branch. Note the application name on the right side pane.

Start > Administrative Tools > Component Services

Expand Component Services, Computers, My Computer, DCOM Config. Scroll down and find the application ( sometimes it is displayed simply as a CLSID)

Right-click on the application (or CLSID 000C101C-0000-0000-C000-000000000046) noted in the previous step, select Properties and select the Security tab

Ensure that the Customize radio button is selected, then click Edit in the Launch and Activation Permissions* section

Add the SharePoint farm account specified in the System log error message, giving it Local Launch and Local Activation permssion (and in some requirements – remote launch / activate permission). Click OK, then OK again.

Restart IIS

* If the radio buttons are greyed out in the Launch and Activation Permissions section of the Security tab, then you need to change the ownership of this registry key by following these steps:

Return to the registry windows you open previously (or repeat steps 1 to 4 above)

Right click on the GUID for the found application that was having issue and select Properties

Click Advanced, and then the Owner tab

Change the owner to local Administrators group. Click OK.

Click on the local Administrators group and grant it Full Control permissions. Do not change the permissions for the TrustedInstaller.

Close Component Services window and re-open it

Now return to step 8 above to grant the Launch and Activation Permissions.

The file system cache on the SharePointer server on which the timer service is running needs to be cleared. Here are the steps as directed by Microsoft to resolve the above error:

Stop the SharePoint 2010 Timer service

Navigate to the cache folder
In Windows Server 2008, the configuration cache is in found here:Drive:\ProgramData\Microsoft\SharePoint\Config
Then locate the GUID folder that has the cache.ini file
(Note: The ProgramData folder may be hidden. To view the hidden folder, change the folder options as required)

Back up the cache.ini file.

Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.

When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.

Double-click the cache.ini file.

On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.

Start the SharePoint 2010 Timer serviceNote: The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

Make sure that the cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the cache.ini file is not 1.

Click the Check Names icon to ensure that the account name can be resolved by the authentication providers on the application server.

In the Choose Permissions section, check the Full Control – Has full control box.

Click Finish.

Repeat Steps 5 – 8 for the Super Reader account.

In the Choose Permissions section, check the Full Read – Has full read-only access box.

Click Finish.

Make note of how the names for the Object Cache Super Reader and Object Cache Super User accounts are displayed in the User Name column. The displayed strings will be different depending on whether you are using claims authentication for the Web application.

Then, add the user accounts to the Web application by using Windows PowerShell

Copy the following code and paste it into a text editor, such as Notepad:$wa = Get-SPWebApplication -Identity “”$wa.Properties[“portalsuperuseraccount”] = “<SuperUser>”$wa.Properties[“portalsuperreaderaccount”] = “<SuperReader>”$wa.Update()

Replace the following placeholders with values:

<WebApplication> is the name of the Web application to which the accounts will be added.

<SuperUser> is the account to use for the Super User account as you saw it displayed in the User Column field mentioned in Step 14 of the previous procedure.

<SuperReader> is account to use for the Super Reader account as you saw it displayed in the User Column field mentioned in Step 14 of the previous procedure.

Save the file, naming it SetUsers.ps1
You can use a different file name, but you must save the file ANSI-encoded as a text file whose extension is .ps1.