Qdabra Database Accelerator

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

Jim Cantwell — Fri, 01 Oct 2010 03:26:25 GMT

You will need to make sure and grant the identity used to have db_datareader and db_datawriter permissions on the QdabraDBXL and QdabraUtilities databases. You may also need to reset the DBXL app pool after granting those permissions.

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

mkirts — Fri, 01 Oct 2010 01:10:24 GMT

Hello!

I'm having the same issue as above, however when i switch the DBXL identity to the same as the SharePoint app pool, I am unable to open the DBXL Admin tool. InfoPath gives me "Form template: http://myserver/qdabrawebservice/forms/dat/template.xsn; The following form template for the form cannot be found: http://myserver/qdabrawebservice/forms/dat/template.xsn

and this in the QDabra event log:

Event Type: ErrorEvent Source: Database AcceleratorEvent Category: NoneEvent ID: 0Description:TemplateHandler GET failure for url http://sharepoint/QdabraWebService/Forms/ID/184/template.xsn encountered a critical error and needs attention:

User: mydomain/myusername

Url: /QdabraWebService/Forms/ID/184/template.xsnDevExpress.Xpo.DB.Exceptions.UnableToOpenDatabaseException: data source=/LM/W3SVC/1956657239/ROOT/QdabraWebService-1-129303658989285545.mdb;password=;user id=Admin;provider=Microsoft.Jet.OLEDB.4.0;mode=Share Deny None ---> System.Data.OleDb.OleDbException: 'c:\LM\W3SVC\1956657239\ROOT\QdabraWebService-1-129303658989285545.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection) at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.OleDb.OleDbConnection.Open() at DevExpress.Xpo.DB.AccessConnectionProvider.CreateDataBase() --- End of inner exception stack trace --- at DevExpress.Xpo.DB.AccessConnectionProvider.CreateDataBase() at DevExpress.Xpo.DB.ConnectionProviderSql..ctor(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider..ctor(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider.CreateProviderFromConnection(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider.CreateProviderFromString(String connectionString, AutoCreateOption autoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.DB.DataStoreBase.QueryDataStore(String providerType, String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.XpoDefault.GetConnectionProvider(String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.Session.ConnectOldStyle() at DevExpress.Xpo.Session.Connect() at Qdabra.Dbxl.WebService.Implementation.DocumentRetrieval.DocumentHandlerImplementation.GetTemplateXsn(Int32 docTypeId, String fileName, DateTime& dateLastModified) at Qdabra.Dbxl.DocumentRetrieval.TemplateHandler.ProcessRequest_GET_or_HEAD(HttpContext context, Boolean isHeadRequest) The stack trace was: at DevExpress.Xpo.DB.AccessConnectionProvider.CreateDataBase() at DevExpress.Xpo.DB.ConnectionProviderSql..ctor(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider..ctor(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider.CreateProviderFromConnection(IDbConnection connection, AutoCreateOption autoCreateOption) at DevExpress.Xpo.DB.AccessConnectionProvider.CreateProviderFromString(String connectionString, AutoCreateOption autoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.DB.DataStoreBase.QueryDataStore(String providerType, String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.XpoDefault.GetConnectionProvider(String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect) at DevExpress.Xpo.Session.ConnectOldStyle() at DevExpress.Xpo.Session.Connect() at Qdabra.Dbxl.WebService.Implementation.DocumentRetrieval.DocumentHandlerImplementation.GetTemplateXsn(Int32 docTypeId, String fileName, DateTime& dateLastModified) at Qdabra.Dbxl.DocumentRetrieval.TemplateHandler.ProcessRequest_GET_or_HEAD(HttpContext context, Boolean isHeadRequest).

Any ideas?

Thanks in advance,

Matthew

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

ErnestoM — Mon, 28 Dec 2009 11:17:01 GMT

This was solved last week:

"This has been resolved. After reviewing her site configuration, I had her check the Application eventlog for errors matching the time of the Qdabra error. There was a SharePoint error at those times with Network Service not having permission to access the Sharepoint database. Evidently, the object model does direct database access. I had her switch DBXL to use the same identity as the SharePoint app pool."

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

ErnestoM — Tue, 22 Dec 2009 14:44:40 GMT

It should be possible to accomplish this scenario (DBXL and Sharepoint on one machine, SQL on another).

You've run into a permissions error, and the problem seems to be happening when the Sharepoint machine tries to log in to the SQL machine.

Are you able to deploy and use a browser-enabled form on this Sharepoint instance (no DBXL)? I suggest you try this next so we can determine whether DBXL is involved in this error. Also, please let us know if there is anything in the Qdabra event log.

Thank you.

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

tgfo62 — Tue, 22 Dec 2009 13:26:32 GMT

The DBXL is installed on my sharepoint server. The SQL server is on a different machine. Here is the error message from the Sharepoint server - event id 3000

Event Type: Error
Event Source: Database Accelerator
Event Category: None
Event ID: 3000
Date:  12/21/2009
Time:  5:01:31 PM
User:  N/A
Computer: MYDELTA
Description:
Caught exception testing connection string. encountered a critical error and needs attention:

System.Data.SqlClient.SqlException: Cannot open database "Deviations" requested by the login. The login failed.
Login failed for user 'DELTADOMAIN\MYDELTA$'.
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Qdabra.Dbxl.WebService.Implementation.ServiceImplementation.TestConnectionString(String ConnectionString, String& ErrorMessage, Boolean& Success)

The stack trace was:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Qdabra.Dbxl.WebService.Implementation.ServiceImplementation.TestConnectionString(String ConnectionString, String& ErrorMessage, Boolean& Success).

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

Re: Error S0002 - Cannot create the Sharepoint library for publishing the form

Jo-Anne Alfafara — Mon, 21 Dec 2009 23:11:08 GMT

Hello,

I'm sorry to hear about the error you are having. Is DBXL installed on the same server as the SharePoint site being submitted to? (same server can use 'Object Model', remote server requires 'Web Service'). Also, can you check your Qdabra log in your event viewer and see if there are any errors there that might give us more information?

Thanks!

Error S0002 - Cannot create the Sharepoint library for publishing the form

tgfo62 — Mon, 21 Dec 2009 18:37:17 GMT

I'm getting the following error when I try to follow the instructions on How to IPFS - enable a codeless dBXL solution
my form does not have code. I get this eror at step 5 of the instructions

S0002: Caught exception ensuring Sharepoint form library http://myserver/eng/Deviations. Cannot open database "M0ss07_ContentMyServer"
requested by the login. The login failed. Login failed for user 'MYdomain\mySERVERNAME$'

I of couse change the name of my server in the message I typed here for privacy.

Thanks,