Updating Form template with DAT - InfoPath Dev
in

InfoPath Dev

Updating Form template with DAT

Last post 04-16-2012 01:54 PM by tenbao. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-16-2012 01:06 PM

    Updating Form template with DAT

    Currently I have a problem with updating an InfoPath template using the DBXL Admin Tool. I have the Qdabra Web service installed on a SharePoint WFE to utilize the SharePoint Object Model. I am able to configure a new InfoPath library by using the "Publish Library and XSN" and "Use Forms Services" checkbox. But when I attach an updated XSN template with additional fields on the "General" tab of the Admin tool and click "Save" to update the InfoPath library template I get the below error:

    An unhandled exception occurred while calling the SetDocmenttype method.

    S0002: Caught exception ensuring SharePoint form library http://xxxxxxx.com/site/InfopathLib. Cannot open log for source 'Database Accelerator'. You may not have write access.

    I'm not sure what kind of permissions are required. The user account is a member of the DBXLAdmins local group on the Qdabra webservice server. Any help would be appreciated. Below is an entry in the Qdabra Event Log:

    Event Type: Error
    Event Source: Database Accelerator
    Event Category: None
    Event ID: 0
    Date:  4/16/2012
    Time:  12:58:32 PM
    User:  N/A
    Computer: XXXXXXXXXXXXXX
    Description:
    An error occurred while setting up a SharePoint collection mapping with the adminstrative tool. This could be a user error. In case it is a system problem, error details have been logged.

    SharePoint URL:
    http://tcwsharedev.corp.tcw.com/lokj/ThousandFields2

    Exception:
    System.InvalidOperationException: Cannot open log for source 'Database Accelerator'. You may not have write access. ---> System.ComponentModel.Win32Exception: Access is denied
       --- End of inner exception stack trace ---
       at System.Diagnostics.EventLog.OpenForWrite(String currentMachineName)
       at System.Diagnostics.EventLog.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
       at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
       at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID)
       at Qdabra.Util.ServiceTool.WriteLog(String fullMessage, EventLogEntryType entryType, LoggingLevel logLevel, Int32 eventId)
       at Qdabra.Util.ServiceTool.LogInformation(String message)
       at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, ICredentials ssoCredentials, DbxlDocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)
       at Qdabra.Dbxl.SharePoint12.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, DbxlDocumentType docType, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)
       at Qdabra.Dbxl.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DbxlDocumentType docType, Session session)

    Stack Trace:
       at System.Diagnostics.EventLog.OpenForWrite(String currentMachineName)
       at System.Diagnostics.EventLog.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
       at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
       at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID)
       at Qdabra.Util.ServiceTool.WriteLog(String fullMessage, EventLogEntryType entryType, LoggingLevel logLevel, Int32 eventId)
       at Qdabra.Util.ServiceTool.LogInformation(String message)
       at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, ICredentials ssoCredentials, DbxlDocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)
       at Qdabra.Dbxl.SharePoint12.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, DbxlDocumentType docType, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)
       at Qdabra.Dbxl.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DbxlDocumentType docType, Session session) encountered a critical error and needs attention.

    User: CORP\LOKJ
    Url: /QdabraWebService/DbxlDocumentService.asmx


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  • 04-16-2012 01:24 PM In reply to

    Re: Updating Form template with DAT

    Hi-

    Usually this error is related to a permissions issue and is generated by a user who has limited permissions to DBXL Document Types or Documents and when Check Out is required in SharePoint. Even after removing the Check Out requirement, you may still get the same error.

    To workaround this issue, a registry change is needed on the server where DBXL is installed. Please proceed with caution. Edit the CustomSD value under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Qdabra]. Append “(A;;0x3;;;S-1-1-0)” at the end of the value (without the quotes). The value should end up looking something like this:

    "O:BAG:SYD:(D;;0xf0007;;;AN)(D;;0xf0007;;;BG)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-1-0)"

    Let us know if this helps, or if you need additional assistance. Thanks.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 04-16-2012 01:54 PM In reply to

    Re: Updating Form template with DAT

    It looks like you're adding the local "Everyone" group to have permission to write to the Qdabra Event Log. Looks like it worked. Thanks.

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.