|
| | | Forum Newbie
 
Group: Forum Members
Last Login: Tuesday, July 14, 2009
Posts: 1, Visits: 12 |
| Good afternoon, I have a 2 server MOSS farm (Database Server - Application Server) and though i installed Skelta without a problem the configuration of a new Repository with Skelta List or Active Directory takes forever with the following results when i try to open the new Repository:
Server Error in '/CentralConfig' Application.
Could not load data for table (SKEntity), No matching record found for column: @Name, value: UserEntity, Repository:1000, severityLevel: Fatal
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Skelta.Core.DS.SingleTableObjectDataRowException: Could not load data for table (SKEntity), No matching record found for column: @Name, value: UserEntity, Repository:1000, severityLevel: Fatal
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SingleTableObjectDataRowException: Could not load data for table (SKEntity), No matching record found for column: @Name, value: UserEntity, Repository:1000, severityLevel: Fatal]
Skelta.Core.DS.SingleTableObject.LoadRowData() +2068
Skelta.Core.DS.SingleTableObject.EnsureRecordsInTableRow() +161
Skelta.Entity.Entity.GetEntity(ApplicationObject application, String name) +222
Skelta.Core.UserLookUpSearch..ctor(String ApplicationName) +102
Skelta.CentralConfigCodeBehind.ConfigAdministrator.PopulateAdminUser() +91
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +42
System.Web.UI.Control.OnLoad(EventArgs e) +132
System.Web.UI.Control.LoadRecursive() +66
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428
Version Information: Microsoft .NET Framework Version:2.0.50727.3074; ASP.NET Version:2.0.50727.3074
-----------------------------------------------------------------------------------------------------------------------
And every 30 seconds in Application Log
? - @#@Date - 7:13:50 μμ.328@#@Module - C:\Windows\assembly\GAC_MSIL\Workflow.NET.NET2\3.5.0.0__c932f724c984e915\Workflow.NET.NET2.dllC:\Windows\assembly\GAC_MSIL\Workflow.NET.NET2\3.5.0.0__c932f724c984e915\Workflow.NET.NET2.dll , Assembly version = 3.5.9027@#@_MachineName - HQNOSPS01, Process - w3wp@#@Message - Exception while Initialize for SqlDataHandler :System.Transactions.TransactionException: The operation is not valid for the state of the transaction.
at System.Transactions.TransactionState.EnlistPromotableSinglePhase(InternalTransaction tx, IPromotableSinglePhaseNotification promotableSinglePhaseNotification, Transaction atomicTransaction)
at System.Transactions.Transaction.EnlistPromotableSinglePhase(IPromotableSinglePhaseNotification promotableSinglePhaseNotification)
at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx)
at System.Data.ProviderBase.DbConnectionInternal.ActivateConnection(Transaction transaction)
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 Workflow.NET.DataHandler.SQLDataHandler.Initialize(CustomConnectionProperties customConnectionPropeties)@#@
In all in one server env/ment no problem at all
|
| |
| | | Supreme Being
Group: Forum Members
Last Login: Monday, December 21, 2009
Posts: 102, Visits: 124 |
| | Hi Parislan, The message "The operation is not valid for the state of the transaction" might appear if the DTC service was not running at that moment or there was some disconnectivity with the DB. So there may be the below mentioned causes for this issue :- 1. The Windows Firewall is "Switched On" on the Skelta/SQL Server machine.
>> Switch Off the Windows firewall on both machines while performing the Skelta Installation/Configuration. 2. The MSDTC Setings are not configured properly on the Skelta/SQL Server machine.
>> Follow the attached screen shot "MSDTC.jpg" for configuring the MSDTC settings on both the machines. 3. You can also verify the MSDTC service settings on the Skelta/SQL Server machine by running the attached tool (TestConnection.zip). >> You need to extract the EXE file of the tool and execute it (run this tool on both the machines). Then, in both the text boxes, provide the connection string to connect to your SQL Server and then click on the buttons one by one and check the output. 4. The required ports for MSDTC service are not opened.
>> Open the below mentioned port-
Port Number and Purpose
135 RPC EPM (end point mapper)
1433 TDS SQL traffic when using TCP/IP
1434 SQL 2000 Integrated Security
5100 - 5200MSDTC (Dynamically assigned a port by the EPM) >> ** Run the tool provided by Microsoft (DTC Tester tool - http://support.microsoft.com/kb/293799) to check if there are any issus with respect to your environment like firewall restrictions/ports being blocked etc. Thanks, Sri
Srinivasa Rao Pentapati |
| |
| | | Junior Member
Group: Forum Members
Last Login: Friday, September 25, 2009
Posts: 5, Visits: 15 |
| Oooppss.. missed the attachments(MSDTC.JPG, TestConnection.zip). Here you go...
|
| |
|
|