ComInitialization property of ServerController

Question

I am new to IntraWeb. I want to make a simple application which connects and displays an access database using ADO controls. When I execute the server it gives me

"CoInitialize has not been called"

error. I searched the internet and found many text telling that

Change ComInitialization property of IWServerController to ciMultiThreaded.

I tried to do this in IWAppFormCreate event. Then I got compilation error:

"Undeclared Identifier ciMultiThreaded"

I put the line IWServerController.ComInitialization:=ciMultiThreaded; then the runtime error comes up:

"Access violation at address . . ."

Since I don't know what I am doing I cant find the problem. Please help me.

Answer 1

The CoInitialize error on IntraWeb using ADO gives you the correct answer.

As I catch from comments on @David answer to this question, there are two things left:

1. Where is declared the TComInitialization type, which in turns defines the ciMultiThreaded identifier. Answer to this is: IWServerControllerBase unit, part of Intraweb.
2. Where to change the ComInitialization property of the IWServerController object to get this working.
   • The first thing you have to know is the actual class used to construct the IWServerController object is part of your IntraWeb project.
   • Next, trying to set this property on a page OnCreate event looks too late (it must be created in the thread you want to initialize COM), my guess is that altering this property at this time is forbidden and will raise an exception, or will be ignored completely.
   • Using the Delphi XE VCL for the Web Application wizard I got a unit named ServerController, with the class TIWServerController. After failing to override the constructor, I override the AfterConstruction method to initialize such property, like this

Example:

  TIWServerController = class(TIWServerControllerBase)
    procedure IWServerControllerBaseNewSession(ASession: TIWApplication;
      var VMainForm: TIWBaseForm);

  private

  protected
    //constructor Create; override;  //failed!!
  public
    procedure AfterConstruction; override;
  end;

  //..

procedure TIWServerController.AfterConstruction;
begin
  inherited;
  ComInitialization := ciMultiThreaded;  //succeded
end;

I then added a button, a label and properly configured ADOConnection (against SQL Server if that matters) and:

procedure TIWForm2.IWButton1Click(Sender: TObject);
begin
  try
    ADOConnection1.Connected := True;
    IWLabel1.Caption := 'Connected';
  except
    on E:Exception do
      IWLabel1.Caption := E.ClassName + ' ' + E.Message;
  end;
end;

Hitting the button, produces this:

Hope this is enough to you.

Answer 2

If you used the IntraWeb Application Wizard in XE2, it would of created a ServerController.pas unit for you.

If you open that unit in the visual designer, and click on the "form", you'll see a slew of properties for the TIWServerController. One of those is ComInitialization, which is a dropdown containing ciMultiThreaded, ciNone, ciNormal. It defaults to ciNone.

Here is the DFM after I changed the ComInitialization property:

object IWServerController: TIWServerController
  OldCreateOrder = False
  AuthBeforeNewSession = False
  AppName = 'MyApp'
  CharSet = 'UTF-8'
  CacheExpiry = 120
  ComInitialization = ciMultiThreaded
  Compression.Enabled = False
  Compression.Level = 6
  Description = 'My IntraWeb Application'
  DebugHTML = False
  DisplayName = 'IntraWeb Application'
  Log = loNone
  EnableImageToolbar = False
  ExceptionDisplayMode = smAlert
  HistoryEnabled = False
  InternalFilesURL = '/'
  JavascriptDebug = False
  PageTransitions = False
  Port = 8888
  RedirectMsgDelay = 0
  ServerResizeTimeout = 0
  ShowLoadingAnimation = True
  SessionTimeout = 10
  SSLOptions.NonSSLRequest = nsAccept
  SSLOptions.Port = 0
  SSLOptions.SSLVersion = sslv3
  Version = '12.0.8'
  OnNewSession = IWServerControllerBaseNewSession
  Height = 310
  Width = 342
end

Hope this helps some.

Answer 3

It sounds like you haven't initialized COM, which you are required to do by calling CoInitializeEx(). From the documentation:

CoInitializeEx must be called at least once, and is usually called only once, for each thread that uses the COM library. Multiple calls to CoInitializeEx by the same thread are allowed as long as they pass the same concurrency flag, but subsequent valid calls return S_FALSE. To close the COM library gracefully on a thread, each successful call to CoInitialize or CoInitializeEx, including any call that returns S_FALSE, must be balanced by a corresponding call to CoUninitialize.