Specializing in Support and Service Software

Browse blog posts about BOLT

• Running Dovetail Classic ASP Web Applications on Vista or Windows Server 2008 64-bit with IIS 7

  When attempting to run any of the Dovetail ASP web applications with Dovetail SDK pre version 3.0 installed. (Agent, Self Service, Admin, etc) on Windows Vista x64 or Windows Server 2008 x64 editions with IIS 7, you may encounter the errors shown below. This is because the default application pools in IIS 7 are set to run in 64-bit mode, but the Dovetail SDK pre version 3.0 was only available as a 32 bit installer. Due to the 32-bit/64-bit Registry Redirection feature in Vista/Server 2008, 64-bit applications cannot see certain registry settings (such as the Dovetail SDK COM compatibility registrations). By enabling 32-bit applications in the web application's application pool, the application will work. See the resolution for specific step-by-step instructions on solving this problem. Here is a sample of the errors you might encounter when the 64-bit/32-bit problems are present: Active Server Pages error '00000000' Create object failed ? An error occurred while creating object 'FCApp'. Active Server Pages error '00000000' Create object failed ? An error occurred while creating object 'FCApp'. FCApplication Initialization Failed. Class doesn't support Automation Active Server Pages error '00000000' Create object failed ? An error occurred while creating object 'FCApp'. Active Server Pages error '00000000' Create object failed ? An error occurred while creating object 'FCApp'. Active Server Pages error '00000000' Create object failed ? An error occurred while creating object 'FCApp'. Initialization Error Application initialization failed. When configuring attachments with the ASP Smart Upload utility (for Dovetail Agent), you might also encounter the following: Microsoft JScript runtime error '800a01ad' Automation server can't create object /client/workflow/44/attachment2.asp, line 87

• ORA-01861: literal does not match format string

  This error is can occur in Oracle when a SQL statement doesn't match the expected format, such as a character or date format. One instance where this was noted was in the business rule usage report in BOLT, when using the Microsoft OLEDB provider for Oracle.

• BOLT error: Provider cannot be found. It may not be properly installed.

  When trying to use BOLT, the following error may occur: Provider cannot be found. It may not be properly installed.

• Timeout expired. The timeout period elapsed prior to completion

  When using a Dovetail product, the following exception can occur: Exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

• Installing web applications on IIS7 (Vista and Widows Server 2008) fails.

  Changes to how Internet Information Server (IIS) is configured have caused problems with installers for Dovetail applications which create virtual web directories. These installer were designed to create virtual directories on IIS 6 You may get an error "Cannot connect to Internet Information Server" or "Failed to read IIsWebs table"