Browsing Solutions For Dovetail SDK

  • Dovetail SDK : Setting the session timeout length using .Net.

    Dovetail SDK sessions have a default timeout of 20 minutes. It is often desirable to change the length of this timeout period.

  • Dovetail SDK session user and sessionid values may not be correct in log files

    The Dovetail SDK and applications written using it commonly write to log files to help administrators troubleshoot problems. Dovetail SDK sets details about the current session (user and sessionid) to the current thread's logging context. These details can then be emitted with the logging pattern. This can cause ambiguity in certain logging situations involving multi-threaded host environment such as a web server. Example logging pattern with session context ``` <layout type="log4net.Layout.PatternLayout"> <param name="ConversionPattern" value="%d [%p] [%c] %m [user: %X{user}] [sessionid: %X{session}]%n" /> </layout> ``` This logging pattern is the default we provide with our SDK based applications. The log below is emitted by a web application whose first request is logged in as 'annie' with a second request (on the same thread) being logged in as 'hank' ``` 2011-12-15 15:03:09,572 [DEBUG] [Dovetail.Agent.Authentication.ClarifySessionCache] Creating missing session for agent annie. [user: (null)] [sessionid: (null)] 2011-12-15 15:03:09,589 [DEBUG] [Dovetail.Agent.Authentication.ClarifySessionCache] Created session e7deb77f-46f1-4cc3-89e0-5eed70c28327 for agent annie. [user: annie] [sessionid: e7deb77f-46f1-4cc3-89e0-5eed70c28327] 2011-12-15 15:03:25,896 [DEBUG] [Dovetail.Agent.Authentication.ClarifySessionCache] Creating missing session for agent hank. [user: annie] [sessionid: e7deb77f-46f1-4cc3-89e0-5eed70c28327] 2011-12-15 15:03:25,903 [DEBUG] [Dovetail.Agent.Authentication.ClarifySessionCache] Created session 31d5c417-b9d0-4df2-af0e-9cf8d6452a50 for agent hank. [user: hank] [sessionid: 31d5c417-b9d0-4df2-af0e-9cf8d6452a50] ``` Notice the second set of logs has the user name and session id of the previous web request. After the session is created the user name and session id are correct. The second request is still logging the user and session id of 'annie'.

  • How to enable logging for the Data Verifier application

    If unexpected problems occur while running the Dovetail Data Verifier application (which can be a separate application, or bundled with the Dovetail SDK product), a Dovetail support person may ask you to enable logging for the Data Verifier and send him/her the logs as well as the test results.

  • System.Threading.ThreadAbortException: Thread was being aborted.

    During FcApplication initialization of the Dovetail SDK (fcSDK), the following error may occur: System.Threading.ThreadAbortException: Thread was being aborted. The stack trace may look something like: [ERROR] [FChoice.Foundation.FCApplication] Error initializing CacheManager and LicenseManager: Thread was being aborted. [user: (null)] [sessionid: (null)] System.Threading.ThreadAbortException: Thread was being aborted. at FChoice.Common.Data.SqlHelper.FillDataSet(DbDataAdapter adapter, DataSet ds, String[] tableNames, IDbConnection connection, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema) at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String[] tableNames, IDbConnection conn, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema) at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String sqlStmt, String[] tableNames, Boolean fillSchema) at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String sqlStmt, String[] tableNames) at FChoice.Foundation.Clarify.StringCache.LoadStringTable(DataSet stringDs) at FChoice.Foundation.Clarify.StringCache.InitCacheData() at FChoice.Foundation.CacheBase.InitializeCache() at FChoice.Foundation.CacheManager.LoadDataCaches(CacheBase[] caches) at FChoice.Foundation.CacheManager.Initialize(CacheBase[] caches, ISchemaCache schemaMaster) at FChoice.Foundation.FCApplication.FCAppInitialize(CacheBase[] caches, ISchemaCache schemaMaster) 2011-11-01 18:31:34,237 [ERROR] [FChoice.Common.Data.SqlHelper] Error while performing a FillDataSet database command [user: (null)] [sessionid: (null)] System.Threading.ThreadAbortException: Thread was being aborted. at System.Data.Common.UnsafeNativeMethods.OCIStmtFetch(OciHandle stmtp, OciHandle errhp, UInt32 nrows, FETCH orientation, MODE mode) at System.Data.OracleClient.TracedNativeMethods.OCIStmtFetch(OciHandle stmtp, OciHandle errhp, Int32 nrows, FETCH orientation, MODE mode) at System.Data.OracleClient.OracleDataReader.ReadInternal() at System.Data.OracleClient.OracleDataReader.Read() at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping) at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue) at System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) at FChoice.Common.Data.SqlHelper.FillDataSet(DbDataAdapter adapter, DataSet ds, String[] tableNames, IDbConnection connection, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema)

  • 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

  • Creating sessions without passwords is disabled for security reasons.

    The following error can be thrown by the fcSDK: Exception calling "CreateSession" with "2" argument(s): "(10158) Creating sessions without passwords is disabled for security reasons. If you wish to allow this potentially unsafe behavior, you must configure the app to allow it. Please consult the documentation on how to enable this setting." Example .NET code that can cause this error: $ClarifySession = $clarifyapp::Instance.CreateSession("sa","User"); Notice that CreateSession is being called with two parameters: a username and a login type. This overload of the CreateSession method creates a new ClarifySession and performs a passwordless login for the specified user and ClarifyLoginType.

  • Creating sessions using the fcSDK application user is disabled for security reasons.

    The following error can be thrown by the fcSDK: Exception calling "CreateSession" with "0" argument(s): "(10159) Creating sessions using the fcSDK application user is disabled for security reasons. If you wish to allow this potentially unsafe behavior, you must configure the app to alloow it. Please consult the documentation on how to enable this setting. Example .NET code that can cause this error: $ClarifySession = $clarifyapp::Instance.CreateSession(); Notice that CreateSession is being called with zero parameters. This overload of the CreateSession method creates a new ClarifySession and logs in using the username and password from the application object.

  • Quick start guide for setting up logging for Dovetail Agent and Dovetail Admin.

    All Dovetail applications that use our SDK have a logging capability that can be enabled. The following steps will get you up and running quickly with SDK logging in Dovetail Agent and Dovetail Admin. Note: There are detailed instructions on customizing logging in the Dovetail SDK documentation.

  • Out of Memory Exception during Distinct Query

    While trying to get a list of distinct sites that have certain parts installed, a customer recently tried to query using FCGenerics and got an error: "System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown." Here is the code that was attempted: Dim gPartNum As ClarifyGeneric = dataSet.CreateGeneric("part_num") gPartNum.AppendFilterInList("part_number", True, ListOfParts()) Dim gModLevel As ClarifyGeneric = gPartNum.Traverse("part_num2mod_level") Dim gSitePart As ClarifyGeneric = gModLevel.Traverse("part_info2site_part") gSitePart.AppendFilter("level_to_bin", NumberOps.NotEquals, 999) Dim gSite As ClarifyGeneric = gSitePart.Traverse("site_part2site") gSite.IsDistinct() = True gSite.Query()

  • Could not find stored procedure 'fc_new_oid'

    Received this error message when trying to log in to Dovetail Agent: Could not find stored procedure 'fc_new_oid'

  • License Exception - Could not obtain license productId [productId]

    If the following licensing exception is preventing your application from being used property: FChoice.Common.FCLicenseException: (5246) Could not obtain license productId [productID] as all user and grace license limits are full or there is no license present for this product. And you are confident that you have a valid Dovetail license for the product. You may be affected by a bug in our licensing mechanism which occurs when you have 2 valid licenses for a single Dovetail product. You can see your licenses by using the License Installer utility included with Dovetail SDK. The problem happens when your second valid license is "better" (more users, later expiration date) than the first license that was found. A bug prevents the second license from properly replacing the first license. This problem occurs in versions of Dovetail SDK versions 3.0 and earlier. Keywords Service won't Product will not start fcSDK

  • Dovetail SDK 64-bit compatibilty a concern when authenticating Contact sessions

    Applications using Dovetail SDK's .Net APIs are, for the most part, 64 bit ready. However, when creating sessions for Contacts (web_users) using the Dovetail SDK in a 64 bit environment your application will throw this exception : System.BadImageFormatException : An attempt was made to load a program with an incorrect format. This exception is related to a 32 bit legacy library required by Dovetail SDK to support backwards compatiblity with how Contact authentication is done in Clarify. This 32 bit dependency is only used when authenticating or administrating the password for a contact's web_user record. This use case is not the norm and should be only encountered by Dovetail customers creating custom applications which create Contact sessions. Keywords 32-bit, 64-bit

  • Dovetail SDK is installed but I cannot get my scripts to run

    When invoking Javascript aor VBScript Dovetail SDK scripts from a command prompt on a Windows 64 bit operating system. You will get an error like one of the following: WScript.CreateObject: Could not create object named "FCFLCompat.FCApplication". Automation server can't create object The error makes it appear that Dovetail SDK is not installed. Note: You may want to double check to see if Dovetail SDK is indeed installed correctly and passing all your Data Verifier tests. Keywords: fcSDK, FCFL.Net

  • Dovetail SDK DataVerifier COM validation fails on 64 bit Windows OS.

    Running the DataVerifier utility included with Dovetail SDK versions earlier than 2.4.8 on 64-bit operating systems will fail the COM validation test. This is happening because Dovetail SDK COM components depend on registry keys that are not installed in 64 bit registry locations. Which happens because the Dovetail SDK's Windows Installer is 32 bit. The COM components need to be invoked from a 32 bit environment to work correctly.

  • Unable to load DLL 'fc_crypt2' error on 64-bit operating systems

    The following error can occur when the fcSDK (or any fcSDK based application such as DovetailAdmin, DovetailAgent, or Dovetail SelfService) needs to deal with an encrypted password (such as during login, or c when setting or changing a password): Unable to load DLL 'fc_crypt2': The specified module could not be found. (Exception from HRESULT: 0x8007007E) This can occur on 64-bit operating systems, such as Windows Server 2008, Vista, and Windows 7

  • How does Dovetail SDK Licensing Work?

    Customers are often curious how Dovetail SDK licensing works. In this solution I will go over: * An introduction to Dovetail SDK licenses and how they work together with Toolkit licenses. * What happens when multiple licenes for the same product are installed? * How do I tell how many product licenses are in use? * When my application restarts do licenses get reset?

  • Platform Guide: List of supported platforms and versions

    Where can I find details on the list of supported platforms for Dovetail products? Keywords: Microsoft SQL Server MSSQL Oracle requirements operating system windows iis .NET Clarify Amdocs

  • Refreshing Dovetail SDK Caches

    Applications which use Dovetail SDK (which are pretty much all applications shipped by Dovetail Software) cache commonly used data to avoid repeated lookups in to the database. Each cache is loaded once, during application initialization. It is common to have objects that are cached get modified during the application's lifespan. When this happens the outdated cache should be refreshed. This article will show you how to refresh the caches at the application level and programatically in your own applications using the Dovetail SDK.

  • Disabling Dovetail SDK file caching

    When Dovetail SDK was initially released back in 2003 it had file caching enabled by default. Dovetail SDK caches common static Clarify system data at application startup (e.g. Schema, Lists, Timezones, States and Countries). File caching would put this cached data into a binary file making it much faster to load start up an application which could load its cached data from file rather than from the database. Over the years this feature has caused a lot of confusion mostly because customers will commonly update the database and wonder why they are still seeing the old their schema or lists coming out of Dovetail SDK. Additionally the performance of networks and databases and computers theses days makes the reduced startup time less noticeable. Dovetail SDK no longer does data caching to file by default and we do not recommend that you use this feature. Keywords: FCFL.Net, fcSDK, list cache, schema cache

  • Information on Unified Login (sometimes referred to as Integrated Windows Security)

    Information on Unified Login (sometimes referred to as Integrated Windows Security)

  • Error in Ship API when using long site names

    When shipping to a site with a name that is longer than 40 characters, this error occurs: (20084) (20141) Invalid string value 'this site name is longer than forty characters' for field 'ship_to_name'. Value must not be longer than 40 characters. Inside the Ship API, the site name is being used to populate a new record on the ship_parts table. The trouble is that the ship_to_name field is 40 characters (in the baseline schema), and the site name is 80 characters (in the baseline schema) - hence the error.

  • 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.

  • How to troubleshoot invalid user-defined lists (hgbst lists)

    When running the Dovetail Data Verifier, customers may find that they have invalid user-defined lists in their system. Troubleshooting these lists can be tough. In order to assist with this, Dovetail has developed the Dovetail HGBST (User-defined Lists) Utility. The HGBST Utility is a command-line utility for Microsoft Windows that helps you visualize your user-defined lists (HGBSTs) and troubleshoot invalid data. If you have previously run the Dovetail Data Verifier and it revealed problems with your HGBST structures, this program will help you determine exactly what to do to fix it.

  • Clarify views that use non-ANSI join operators will fail in SQL Server 2008

    After upgrading to MS SQL Server 2008, querying specific views results in the following error: "The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility level for current database to 80, using the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes."

  • 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"

  • Debugging Fulfill API Issues

    The Fulfill API can throw an exception for many reasons - bad input data, inconsistent part inventory, etc. When troubleshooting a Fulfill API issue, the following information will be useful:

  • Using Dovetail Software products with 32bit Oracle drivers can cause ORA-12154 error

    When running a Dovetail Product that is using 32bit Oracle drivers, a user may encounter a message as follows: ORA-12154: TNS:could not resolve the connect identifier specified The above message should be displayed to the user, or located in log files for the product being used. As an example, Dovetail Schema Editor shows the following: "Error Occurred : Database settings in "Default.SchemaEditor" are not valid. Please confirm that database type and connection string are correct." Within the SchemaEditor.log file, the following exists: 2010-10-12 14:44:51,259 ERROR Dovetail.DataDictionary.Persistence.Database.SqlHelperAdapter - Database connection could not be made: ORA-12154: TNS:could not resolve the connect identifier specified System.Data.OracleClient.OracleException: ORA-12154: TNS:could not resolve the connect identifier specified This issue is not specific to Dovetail applications, but is a known Oracle bug with respect to the path used for Oracle 32 bit software. Typically this occurs in 64bit OS environments where (by default) Windows likes to install 32-bit apps into the C:\Program Files (x86)\... folder. The problem is in the C:\Program Files (x86)\ directory name - specifically, the parenthesis. Calls made to the 32bit drivers fail because the calling program information is passed to Oracle, where it takes the () as a special command. Oracle Article ID 334528.1 provides detailed information (login required): https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=334528.1

  • fcSDK Install issues or problems

    Error installing fcSDK: >> “failed to read IISWebstable (-2147023728)” keywords: IIS Installer fcSDK Wix Webs table Failed to read IIsWebs table

  • case history not being updated via classic client

    In Clarify 11.5 and 12.5, if the case modify stamp value (modify_stmp) contains millisecond values (ex: 2006-12-24 10:23:14.110) instead of '000' milliseconds, then some of the case history is missing. Steps to reproduce: Using the Classic Client, create a case Using the fcSDK or fcClient, log a note to the case. View the case in the classic client - the notes are shown in the case history. Using the classic client, log a note to the case View the case in the classic client - the notes are NOT shown in the case history.

  • Protecting sensitive data using Configuration Protector

    Some configuration settings can contain sensitive information such as usernames and passwords. fcSDK can protect such sensitive settings using Data Protection. The Dovetail SDK includes a Configuration Protector utility: Start - Programs - FCSDK - Configuration Protector You can use this utility to encrypt sensitive data, such as your database connection string. Important Note: The encrypted key can only be decrypted on the same machine from which it was encrypted on. For example, if you want to use this encrypted key on your web server, then you should run the Configuration Protector application on your web server. Additional information is available in the SDK documentation: http://www.dovetailsoftware.com/user_guides/dovetailSDK/2.4.8.9160/html/fcsdk_config_basic.html#dataprotection

  • How do I enable logging of windows installer failures?

    Problems can crop up with windows installers. If you do not have permissions or a required subsystem is missing you can get weird errors. When you open a case with us regarding installation issues we will likely ask that you send us an installer log. Below are instructions on how to get a log of the results of an failure to install one of our MSI installers.

  • SDK install error: "Cannot connect to Internet Information Server"

    When installing the SDK on a server that does not have IIS installed, users may receive the following error: "Cannot connect to Internet Information Server. (-2147221164 )" The user is given the option to Cancel, Retry or Ignore the install. Keywords: IIS SDK install connect 2147221164

  • How to tell if a FCSession is logged in or not.

    Is there a way to tell if a FCSession is logged in or not?

  • Dovetail SDK: changing ClarifySession settings do not take effect across session retrievals when using Remote sessions

    If you do not call SaveSession after making changes to your ClarifySession settings or contents and you are using Remote Sessions, subsequent session retrievals will not reflect your changes.

  • ObjIds of table records are negative when created using Dovetail SDK.

    When a table has 1.88 billion rows or more commonly when Clarify thinks that a table has 1.88 billion records new records created by Dovetail SDK based applications will have negative objids. The objid used when creating new records in Clarify is calculated by looking in the adp_tbl_oid table. Each table in the database has a record in the adp_tbl_oid table indicating the maximum objid in use. For a Clarify database with a 'site_id' of 1 (the default value), when this number grows to be about 1.88 billion (1879048192 to be exact) future objids created by the Dovetail SDK will be negative. Clarify uses a 32 bit signed integer for the objid with an offset of 2^27 (268435456) for the default database 'site_id'. When adding the default base objid to 1879048192) an integer overflow will occur causing the objid to go negative and become -2147483648. Negative objids cause problems when code is assuming identifiers will always be positive and weird errors can result.

  • Error when creating a lead: You must specify a valid site type.

    When using the create_lead API within the Dovetail SDK, the API may throw an error. Error code: -5 Error: You must specify a valid site type. This happens when the site type parameter is left blank. This error can occur even if a site_name is not passed in. COM API: create_update_lead .NET API: CreateLead

  • Cannot connect to Internet Information Server

    The following error can occur when a Dovetail application installer is attempting to create an IIS virtual directory for a web application being deployed: Cannot connect to Internet Information Server. One of the reasons this error can occur is related to a name change to the default IIS web site. The installer is looking for a web site named "Default Web Site". When the name of this web site has been changed you will get the error above. To confirm this is the problem you can turn on windows installer logging. The following solution tells you how to do this: http://www.dovetailsoftware.com/resources/solutions/182_How_do_I_enable_logging.aspx Within this log you will see this error when a renamed Default Web Site is to blame: ConfigureIIsExec: A matching web object in memory was found, but the web object in memory has no associated base ConfigureIIsExec: Error 0x80070002: Failed to find Web base ConfigureIIsExec: Error 0x80070002: Failed to get base of web: DefaultWebSite for VirtualDir ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs

  • Could not log in user ... invalid username or password.

    The error below is common during session creation when something goes wrong related to the credentials being used to connection to the database. 2009-11-02 12:43:39,932 ERROR FChoice.Foundation.FCInvalidLoginException - FChoice.Foundation.FCInvalidLoginException: (10101) Could not log in user 'Sa', invalid username or password.

  • fcSDK error: Object reference not set to an instance of an object

    When updating a record using the fcSDK, the following error can occur: Object reference not set to an instance of an object

  • Information on use of Oracle 11 Database Instant Client

    Information on use of Oracle 11 Database Instant Client with Dovetail applications

  • How to configure timeout for in-memory in Dovetail SDK sessions

    How to configure timeout for in-memory fcSessions for ASP or other COM based applications.

  • Can I avoid rebooting after uninstalling Dovetail SDK?

    When upgrading to a new versions of the Dovetail SDK on a machine running Dovetail web applications it is common to have to reboot the machine because of files that are locked by the web server. You can easily avoid a reboot by shutting down all Dovetail SDK based applications before upgrading.

  • Recommendation: Do not use the system administrator database users as the Dovetail SDK application user.

    Companies will often run their Dovetail/Clarify CRM application with system administrator (sa) credentials. This behavior poses a security risk and is not recommended. Applications based on the Dovetail SDK have what is called an "application user" whose credentials are used to connect to the database and at times used default session user. It can be handy for this user to have elevated privileges when you need to do administrative things like reset passwords. However it can also be a vector for attack. We recommend that you restrict your application user to have a minimum set of privileges.

  • Details about create_employee on Microsoft SQL Server

    The create_employee API within the Interfaces toolkit (fcinter) is used to create new users/employees in the system. As Clarify uses the database for storing and validating user logins and passwords, part of the create_employee API is creating a user and login at the database level as well. In Microsoft SQL Server 7 and 2000, the proper way to do this is using the sp_adduser and sp_addlogin system stored procedures, which the API does. However, sp_adduser requires that the executing user be a DBO (database owner). When using Dovetail Admin (fcAdmin) to create a new employee, the application user (meaning the user defined in the fc.env file) is the user connecting to the database, and this is the user who would be executing sp_adduser and sp_addlogin. So, if you will be using fcAdmin for creating employees, be aware that the user defined in fc.env should be a DBO. If the application user does not have proper permissions, the database will throw an error, such as: User does not have permission to perform this action As of SQL Server 2005, there are two new features available: CREATE USER and CREATE LOGIN. These functions replace the sp_adduser and sp_addlogin features. According to http://msdn2.microsoft.com/en-us/library/ms143729.aspx, sp_adduser and sp_addlogin are supported in the next version of SQL Server (2008), but will be removed in a later version. The specific version of SQL Server has not been determined. These new CREATE functions allow finer grain security access control, so the executing user does not need to be a DBO, but the user does need db_securityadmin and db_accessadmin roles.

  • Dovetail SDK Web Service calls return a Could Not Load Assembly error

    Trying to use Dovetail SDK Web Services on a machine where the Dovetail SDK installer has not been run will result in the following error when trying to invoke web service API calls. Parser Error Message: Could not load the assembly 'FChoice.WebServices.Clarify, Version=2.3.13.8117, Culture=neutral, PublicKeyToken=48c955ba8dfd90d8'. Make sure that it is compiled before accessing the page. Source Error: Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="FChoice.WebServices.Clarify.Global, FChoice.WebServices.Clarify, Version=2.3.13.8117, Culture=neutral, PublicKeyToken=48c955ba8dfd90d8"%> Note: The version number may change.

  • Error changing a password to a string starting with non letter characters

    Affects: Any application that uses the Dovetail SDK against an Oracle database Users will get the following error when attempting to change their password to a string that starts with anything other than a letter. ORA-00988: missing or invalid password(s)

  • Web Services and Demo applicaitons error - Could not load file or assembly 'log4net'

    The Dovetail SDK Web Services application and WebForms and WebServices client demos have a configuration problem in their application configuration file (web.config) in versions of Dovetail SDK through 2.3.9. When trying to use web services or the demo applications you may see an error like the following: An error occurred creating the configuration section handler for log4net: Could not load file or assembly 'log4net' or one of its dependencies. The system cannot find the file specified.

  • Where are numbering schemes defined?

    Where are numbering schemes defined?

  • Installing updates to Dovetail SDK requires that you uninstall existing versions.

    When installing newer versions of Dovetail SDK with an older version of the SDK already present. You will see a dialog that ask you if you want to 1) Modify 2) Repair or 3) Remove Dovetail SDK.

  • Adding Unicode text to the TABLE_ACT_ENTRY.ADDNL_INFO field can throw an error if the DB is not set up as a Unicode DB

    An ORA-12899: value too large for column "TABLE_ACT_ENTRY"."ADDNL_INFO" (actual: 260, maximum: 255) error can occur when calling the FChoice.Toolkits.Clarify.Support.SupportToolkit.LogCaseNote if the data being passed has 255 characters that include Unicode characters.

  • Datetime localization issues can occur when APIs are invoked using non-US cultures.

    In earlier versions of the fcSDK invalid date string errors could occur when the APIs were invoked using non-US date formats.

  • Changing a setting on Session does not have any effect

    CreateCase was not truncating string fields after setting TruncateStringFields = true - instead it was throwing an exception. The error from the log file was: FChoice.Foundation.Clarify.Compatibility.CompatibilityException: (20141) Invalid string value '6666666666666666666666666666666' for field 'x_pin'. Value must not be longer than 8 characters.

  • fcSDK on Clarify 6 (CFO 98)

    The fcSDK assumes that there is certain baseline schema present. Specifically, it assumes the following columns are present: table_state_prov.display_order table_string_db.translate_ind These columns exist in Clarify 7, but not in Clarify 6.

  • fcSqlExec limitation in Unicode characters when connecting to a different database

    The fcSDK COM interface allows programmers to use an fcSqlExec object. fcSqlExec is commonly used to execute arbitrary SQL against your Clarify/Dovetail database. fcSqlExec is only used in COM environments (JavaScript, VB6, VBScript, etc.) fcSqlExec will return an ADO recordset of data, which is compatible with the old FCFL based fcSqlExec object. Essentially, fcSqlExec is a wrapper around ADO. fcSqlExec also allows you to connect to another database, different than your Clarify/Dovetail database. If your Clarfy/Dovetail database is not configured for Unicode, but the "other" database is Unicode-enabled, then the result set from performing an fcSqlExec query against the other database may not properly preserve Unicode characters. This is because fcSqlExec bases its Unicode/Non-Unicode configuration on how the Clarify/Database is configured.

  • Does the user credentials in the application connection string need to be a valid clarify user?

    Applications that use the Dovetail SDK need to specificy a database connection string containing the application user credentials. It is easy to think that the application user credentials used may need to be a valid clarify user. Is this true?

  • Error installing fcSDK: Error writing to file: FChoice.Common.dll.

    Installing the fcSDK errors: Executing op: AssemblyCopy(SourceName=FCHOIC_2.DLL|FChoice.Common.dll,SourceCabKey=gac fileCommon.dll,DestName=FChoice.Common.dll,Attributes=0,FileSize=167936, PerTick=32768,,VerifyMedia=1,,,,,ComponentId={442D5887-A792-44A0-B56B-23 5DA028F8E6},IsManifest=1,,,AssemblyMode=0,) Error 1304. Error writing to file: FChoice.Common.dll. Verify that you have access to that directory. Error installing fcSDK : The installer has encountered an unexpected error. The error code is 2350.

  • There is no script engine for file extension ".js".

    Trying to use cscript to execute a Javascript script can result in the following error: Input Error: There is no script engine for file extension ".js".

  • Error viewing CHM files: The page cannot be displayed

    Trying to read can result in the CHM file showing an error such as "The page cannot be displayed". There are several possible reasons why your CHM e-books and documentation files are unreadable.

  • ADODB.Fields error when calling GetTimeZoneList

    When calling fcApplication.GetTimeZoneList(), the following error can occur: ADODB.Fields: Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another. This can happen with other methods that return an ADO recordset.

  • fcSDK Issue when attempting to cache unexpected data types

    During the FCApplication Initialization, the fcSDK can throw an exception, such as: FChoice.Common: (5036) Unexpected DataSet row data type 'System.Byte[]' while reading dataset from cache file. Not supported. OR Unexpected DataSet row data type 'System.Guid' while reading dataset from cache file. 2007-06-19 09:54:37,157 [user: (null)] [Thread: 976] [fcsessionid: (null)] [ERROR] [FChoice.Common.CommonException] FChoice.Common.CommonException: (5036) Unexpected DataSet row data type 'System.Byte[]' while reading dataset from cache file. Not supported. at FChoice.Common.Data.DataSetSurrogate.a(BinaryWriter A_0, Type A_1, Object A_2) at FChoice.Common.Data.DataSetSurrogate.WriteBinary(DataSet ds, Stream str) at FChoice.Foundation.CacheBase.PersistCacheData(Object cacheData, String filePath) at FChoice.Foundation.CacheBase.b() at FChoice.Foundation.CacheManager.a(CacheBase[] A_0) at FChoice.Foundation.CacheManager.a(CacheBase[] A_0, ISchemaCache A_1) at FChoice.Foundation.FCApplication.FCAppInitialize(CacheBase[] caches, ISchemaCache schemaMaster) at FChoice.Foundation.Clarify.ClarifyApplication.InitializeInternal(NameValueCollection configValues, CacheBase[] caches, ISchemaCache schemaMaster) at FChoice.Foundation.Clarify.ClarifyApplication.Initialize(NameValueCollec

  • Sql Server connectivity issues

    One customer reported an intermittent problem connecting to microsoft sql server 7 (mssql 7) using fcClient and the fcSDK after upgrading to the 2.0 version of the .NET Framework. Random errors could occur, including: Warning: File /client/fsglog/grid_logistics.asp Line 126 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server). . This connectivity issue was also seen when using Data Verifier: Initialize ClarifyApplication Verifies that FCFL.NET can be initialized against this database Error initializing FCFL.NET ClarifyApplication System.Data.SqlClient.SqlException: General network error. Check your network documentation. Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at FChoice.Foundation.Clarify.DataVerifier.Core.FcflNetDomainVerifier.TestClarifyApplication(NameValueCollection envVals) at FChoice.Foundation.Clarify.DataVerifier.Core.FcflNetVerifier.c(NameValueCollection A_0)

  • "Specified cast is not valid" error is table_hgbst_show.last_mod_time is NULL

    If table_hgbst_show.last_mod_time is NULL, then fcSDK and DataVerifier both throw an error: "Specified cast is not valid" stack trace: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidCastException: Specified cast is not valid. at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringShow..ctor(Int32 A_0, DataRow A_1) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringElement..ctor(Int32 A_0, DataRow A_1) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringElementCollection.CreateDataObject(DataRow row) at FChoice.Foundation.DataObjects.DataObjectCollection.Initialize(DataRow[] rows) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringElementCollection..ctor(Int32 A_0, DataRow[] A_1) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringShow..ctor(Int32 A_0, DataRow A_1) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringList..ctor(DataRow A_0) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringListCollection.CreateDataObject(DataRow row) at FChoice.Foundation.DataObjects.DataObjectCollection.Initialize(DataTable table) at FChoice.Foundation.Clarify.DataObjects.HierarchicalStringListCollection..ctor(DataTable A_0) at FChoice.Foundation.Clarify.ListCache.LoadCacheData(Object cacheData) at FChoice.Foundation.CacheBase.b() at FChoice.Foundation.CacheManager.a(CacheBase[] A_0) at FChoice.Foundation.CacheManager.a(CacheBase[] A_0, ISchemaCache A_1) at FChoice.Foundation.FCApplication.FCAppInitialize(CacheBase[] caches, ISchemaCache schemaMaster) at FChoice.Foundation.Clarify.ClarifyApplication.InitializeInternal(NameValueCollection configValues, CacheBase[] caches, ISchemaCache schemaMaster) at FChoice.Foundation.Clarify.ClarifyApplication.Initialize(NameValueCollection configValues) at FChoice.Foundation.Clarify.Compatibility.FCApplication.Initialize()

  • OCI-22053: overflow error

    Performing a query with a decimal field on Oracle using the fcSDK can throw an error: OCI-22053: overflow error One particular customer saw this error when viewing a ClearContracts contract in fcClient. The total_net column is defined as decimal (19,4), meaning that there should only be 4 digits after the decimal point. But, the data being stored was 7480.2199999999999999999999878

  • Enabling Storage of Unicode Data

    The fcSDK is fully Unicode-ready. Fields in your database can be flagged as Unicode fields and the fcSDK will process data in these columns correctly.

  • fcClient: Notifications when license limits are near

    The fcSDK is responsible for tracking and enforcing licensing. There is typically a license limit, then a small number of grace licenses that can be used. For example, you may have 50 licenses and 3 grace licenses. Applications that use the fcSDK (such as fcClient and fcSelfService) can be configured to notify an administrator when the licensing has started to use grace licenses, and when the total limit has been reached.

  • Error: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect

    Performing a query, especially one that involves a traversal ( traversefromparent , traversefromroot, etc.) can thron an unexpected error: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.

  • fcSDK Installer ends prematurely then uninstall fails to remove fcSDK

    The fcSDK installer through version 2.2.2 requires that the .Net 1.1 framework be present, although it doesn't properly verify this requirement. If only the .Net 2.0 framework is present the installer will fail and then become 'wedged' and fail to be uninstalled or re-installed. As of fcSDK version 2.3, the fcSDK installer will verify that .NET 1.1 SP1 is installed. If .NET 1.1 SP1 is not installed, then the fcSDK installer will notify the user, and prevent the install from continuing.

  • What data is cached by the fcSDK?

    What data is cached by the fcSDK?

  • fcSDK Error: This row has been removed from a table and does not have any data.

    fcSDK can throw an error: System.Data (0x80131928) This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row.

  • difference in demand_dtl2pick_part relation between classic clarify and fccl.fulfill API

    The fcSDK is not clearing or updating the demand_dtl relations correctly in the PFSR processes.

  • How to set the default TimeZone in Clarify

    By default Clarify will have a timezone of 'No Time Zone Specified' which is basically GMT. fcClient uses this default timezone when users login to automatically select their timezone if they have not already specified a preference. The fcSDK (and thus fcClient) utilizes this default timezone to set the FCApplication.ServerTimezone. All date times submitted to the system are converted from the session user's timezone to the server timezone. Thus if a user is logged into the system with their timezone set to 'Central Standard Time' and the server has 'No Time Zone Specified' (GMT), 5 hours will be added to any datetimes submitted by that user. This solution covers how to set the Default timezone.

  • How do I know which version of MDAC, ADO, OLEDB I have installed on my computer?

    How do I know which version of MDAC I have installed on my computer? There are multiple ways to do this - so view the multiple resolutions to this solution and use the one most appropriate for you. Keywords: MDAC, ADO, OLEDB, FCFL

  • Recommended Application Protection for First Choice Web Apps

    Recommended Application Protection for First Choice Web Apps (fcClient, fcAdmin, fcSelfService)

  • "Class doesn't support Automation" error thrown by fcSDK API Toolkit COM Compatibility Layer

    When calling various toolkit APIs on the fcSDK API Toolkit COM Compatibility Layer, you may receive an error: "Class doesn't support Automation".

  • fcSDK Web Demo install fails with error " Mapping of accounts did not occur.."

    During the install of the fcSDK web demo an error can occur if ASP.NET is not setup properly on the target machine.

  • FCApp.Log can result in log entries with the wrong session user

    For web applications output of session information from FCApp.Log( message ) can be confusing in the rare situation that it is called before the current page creates its FCSession object. The reason for this is that web applications reuse threads between web pages and the session context information for logging is stored in Thread Local Storage (TLS) during authentication. Thus when you create a retrieve a session via SessionId the current thread saves a bit of information about the current session's user for logging purposes to TLS. In the scenario where FCApp.Log() is called before a session is created the log will receive information from the previous user. It is easy to tell what logs are created via FCApp.Log() as their logger has the title 'FChoice.Foundation.FCApplication' and if this scenario is happening you will likely see the user being the same user from previous log output. Example: 2005-11-02 12:01:22,093 [user: gary] [fcsessionid: 69332bac-e635-4369-8fe8-12460f813b25] [DEBUG] [FChoice.Common.Data.SqlHelper] FillDataSet with existing transaction called. 2005-11-02 12:01:22,218 [user: gary] [fcsessionid: 69332bac-e635-4369-8fe8-12460f813b25] [INFO ] [FChoice.Foundation.FCApplication] inc_page_init strSessionId= The trouble here is that user 'kevin' was the one that actually caused the second log entry. Thus you can see that this situation can be very confusing when using log files to debug issues you may be having.

  • Databinding with ClarifyGeneric objects

    When creating ASP.NET or Windows Forms applications is can be very handy to use .NET's databinding capabilites. This solution will walk you through a basic example of populating a ClarifyGeneric add using the underlying DataSet object in a databinding scenario.

  • fcSDK Installer fails on bad MDAC version (Requires 2.7)

    The fcSDK installer checks the registry to see what version of the MDAC you have installed. It does not proceed if you have a version less than 2.7. The registry key it checks is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer

  • Toolkits APIs with contact sessions that do not specifying usernames can error.

    The fcSDK Toolkit API is called using a Contact based session and the username property on the API call is not set. The API will attempt to use the "user.id" of the session as the default user the API's action will be logged under. This attempt fails as a Contact based session (contact login) does not have a "user.id" as they are not a user. For example, calling fcinter.create_interact with the user_name parameter set to an empty string can result in the following error: Input string was not in a correct format