I am trying to access a 3rd party asmx service (from my ASP.Net MVC 4 app). Mostly it works fine, then suddenly I start seeing an error:
The connection was not closed. The connection's current state is open.
This issue goes away for some time and everything works fine. Then it appears again.
I suspected proxy or network settings but changing those did not help. I am able to 'update service reference' without issues which means I can access the service properly.
Is it possible that this error is generated at the service end and is bubbling to my app?
Can I determine if the issue is at the client end or mine?
Thanks
Details:
[System.ServiceModel.FaultException]: {"Server was unable to process request. ---> The connection was not closed. The connection's current state is open."}
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
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 MyTDI.ClientWebServices.TDIWS_SalesManagement.WS_SalesManagementModuleSoap.GetAgentCommissions(String Agency_RegNo, DateTime StartDate, DateTime EndDate, Int32 PageNo)
at MyTDI.ClientWebServices.TDIWS_SalesManagement.WS_SalesManagementModuleSoapClient.GetAgentCommissions(String Agency_RegNo, DateTime StartDate, DateTime EndDate, Int32 PageNo) in d:\Projects\TPLTDI\MyTDIPortal\MyTDI.ClientWebServices\Service References\TDIWS_SalesManagement\Reference.cs:line 111
at MyTDI.ClientWebServices.Sales.SalesManagementWebService.ListAgentCommissions(String agentId, DateTime startDate, DateTime endDate, Int32 pageNo) in d:\Projects\TPLTDI\MyTDIPortal\MyTDI.ClientWebServices\Sales\SalesManagementWebService.cs:line 31
Code
DataSet ds = null;
using( WS_SalesManagementModuleSoapClient client = new WS_SalesManagementModuleSoapClient( ) )
{
try
{
ds = client.GetAgentCommissions( agentId , startDate , endDate , pageNo );
}
catch( Exception ex )
{
logger.Error( ex , "" );
throw new Exception( "Unable to obtain commissions data from server." );
}
}
The error occurs in the database connection. Make sure that the SqlConnection object is properly disposed in your server code (a good practice is to wrap your code with using statements).
Related
I'm developing a plugin were i have done something like this code
[ChildActionOnly]
[HttpPost,ActionName("Configure")]
[FormValueRequired("test")]
public ActionResult TestSms(SmsRobiModel model)
{
bd.com.robi.bmpws.CMPWebService objCmpService = new bd.com.robi.bmpws.CMPWebService();
bd.com.robi.bmpws.ServiceClass sc = objCmpService.SendTextMessage("username", "password", "sendernumber", "receivernumber", "test msg");
}
but I get an error on this line and here is the error:
bd.com.robi.bmpws.ServiceClass sc = objCmpService.SendTextMessage("username", "password", "sendernumber", "receivernumber", "test msg");
Getting an error when try to consume soap service from nopCommerce.
I am trying to develop a SMS plugin in nopCommerce. I did everything for
a plugin but the sms send method is not functioning.
A SMS provider give me a soap service URL. I added it into my class library project, build it and install it in nopCommerce.
I am getting this error:
System.Net.WebException: The request failed with an empty response. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Nop.Plugin.SMS.Robi.bd.com.robi.bmpws.CMPWebService.SendTextMessage(String Username, String Password, String From, String To, String Message) at Nop.Plugin.SMS.Robi.SmsRobiProvider.SendSms(String text, Int32 orderId, SmsRobiSettings settings) at Nop.Plugin.SMS.Robi.OrderPlacedEventConsumer.HandleEvent(OrderPlacedEvent eventMessage) at Nop.Services.Events.EventPublisher.PublishToConsumer[T](IConsumer`1 x, T eventMessage) in d:\MahadyLiveProjects\eshoptest\Libraries\Nop.Services\Events\EventPublisher.cs:line 40
We are a team where everyone of us experience this somewhat random error. The error is listed below and appears on the line: UserPrincipal.FindByIdentity(principalContext, windowsPrincipal.Identity.Name);
It works just fine several days/weeks/months, and then one of us get this error.
On our test server, where we do not deploy changes to as frequently as our local machines, it works for many months before we get this error.
If we change the application pool from ApplicationPoolIdentity to NetworkService, that works. However, after switching back to ApplicationPoolIdentity the same error appears.
IISreset does not help.
Rebooting the computer always solves the problem, so the ApplicationPoolIdentity has no problems to authenticate us on a daily basis.
This is the code (somewhat modified) that we use:
var windowsPrincipal = principal as WindowsPrincipal;
if (windowsPrincipal == null)
return null;
try
{
var principalContext = new PrincipalContext(ContextType.Domain);
var userPrincipal = UserPrincipal.FindByIdentity(principalContext, windowsPrincipal.Identity.Name);
if (userPrincipal == null) return null;
return userPrincipal.Surname;
}
Here is the error message:
An operations error occurred.
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: System.DirectoryServices.DirectoryServicesCOMException: An operations error occurred.
Source Error:
var principalContext = new PrincipalContext(ContextType.Domain);
var userPrincipal = UserPrincipal.FindByIdentity(principalContext, windowsPrincipal.Identity.Name);
Stack Trace:
[DirectoryServicesCOMException (0x80072020): An operations error occurred.
]
System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) +628309
System.DirectoryServices.DirectoryEntry.Bind() +44
System.DirectoryServices.DirectoryEntry.get_AdsObject() +42
System.DirectoryServices.PropertyValueCollection.PopulateList() +29
System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) +63
System.DirectoryServices.PropertyCollection.get_Item(String propertyName) +163
System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer() +521413
System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit() +51
System.DirectoryServices.AccountManagement.PrincipalContext.Initialize() +161
System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx() +42
System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate) +29
System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(PrincipalContext context, String identityValue) +81
If you are not disposing it in a finaly block, you'll eventually run out of resources...
Using (var principalContext = new PrincipalContext(ContextType.Domain))
{
var userPrincipal = UserPrincipal.FindByIdentity(principalContext,
windowsPrincipal.Identity.Name);
if (userPrincipal == null) return null;
return userPrincipal.Surname;
}
should help
Here is an example of one of our data calls in our DAL using Dapper.Net:
/// <summary>
/// Handles db connectivity as Dapper assumes an existing connection for all functions
/// Since the app uses three databases, pass in the connection string for the required db.
/// </summary>
/// <returns></returns>
protected static IDbConnection OpenConnection(string connectionStringName)
{
try
{
connection = new SqlConnection(WebConfigurationManager.ConnectionStrings[connectionStringName].ConnectionString);
//connection = SqlMapperUtil.GetOpenConnection(connectionStringName); // if we want to use the Dapper utility methods
//connection = new SqlConnection(connectionString);
connection.Open();
return connection;
}
catch (Exception ex)
{
ErrorLogging.Instance.Fatal(ex); // uses singleton for logging
return null;
}
}
public string GetNickname(int profileID)
{
string nickname = string.Empty;
using (IDbConnection connection = OpenConnection("PrimaryDBConnectionString"))
{
try
{
var sp_nickname = connection.Query<string>("sq_mobile_nickname_get_by_profileid", new { profileID = profileID }, commandType: CommandType.StoredProcedure);
nickname = sp_nickname.First<string>();
}
catch (Exception ex)
{
ErrorLogging.Instance.Fatal(ex);
return null;
}
}
return nickname;
}
The consistent errors we are seeing are as follows:
2012-06-20 11:42:44.8903|Fatal|There is already an open DataReader
associated with this Command which must be closed first.| at
System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand
command) at
System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
method, SqlCommand command) at
System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
Boolean async) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String
method, DbAsyncResult result) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String
method) at
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at
System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior
behavior) at
System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
at MyApp.DAL.DapperORM.SqlMapper.d_131.MoveNext() in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\Dapper\SqlMapper.cs:line
581 at System.Collections.Generic.List1..ctor(IEnumerable1
collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1
source) at MyApp.DAL.DapperORM.SqlMapper.Query[T](IDbConnection
cnn, String sql, Object param, IDbTransaction transaction, Boolean
buffered, Nullable1 commandTimeout, Nullable1 commandType) in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\Dapper\SqlMapper.cs:line
538 at
MyApp.DAL.Repositories.MemberRepository.AddNotificationEntry(NewsfeedNotification
notificationEntry) in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\MemberRepositories\MemberRepository.cs:line
465 2012-06-20 11:42:45.2491|Fatal|Invalid attempt to call Read when
reader is closed.| at
System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
at System.Data.SqlClient.SqlDataReader.Read() at
MyApp.DAL.DapperORM.SqlMapper.d_131.MoveNext() in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\Dapper\SqlMapper.cs:line
597 at System.Collections.Generic.List1..ctor(IEnumerable1
collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1
source) at MyApp.DAL.DapperORM.SqlMapper.Query[T](IDbConnection
cnn, String sql, Object param, IDbTransaction transaction, Boolean
buffered, Nullable1 commandTimeout, Nullable1 commandType) in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\Dapper\SqlMapper.cs:line
538 at MyApp.DAL.DapperORM.SqlMapper.Query(IDbConnection cnn,
String sql, Object param, IDbTransaction transaction, Boolean
buffered, Nullable1 commandTimeout, Nullable1 commandType) in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\Dapper\SqlMapper.cs:line
518 at MyApp.DAL.Repositories.MemberRepository.GetBuddies(Int32
profileID) in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\MemberRepositories\MemberRepository.cs:line
271 2012-06-20 11:43:01.2392|Fatal|Sequence contains no elements| at
System.Linq.Enumerable.First[TSource](IEnumerable`1 source) at
MyApp.DAL.Repositories.MemberRepository.GetNickname(Int32 profileID)
in
C:\Projects\Git\MyApp\MyApp.DAL\MyApp.DAL.MyAppPrimary.Repositories\MemberRepositories\MemberRepository.cs:line
337
Initially I had the returns inside the using {...} and moved them outside the using block, but still experiencing the same issues.
This is a high-traffic application, so in testing this issue didn't really come up until we went live.
Is there something else that has to be done here for DataReader management with Dapper?
----- UPDATE -----
I should have posted this earlier, but just adding this now.
Line 581 of the Dapper.Net contains the ExecuteReader() code:
private static IEnumerable<T> QueryInternal<T>(this IDbConnection cnn, string sql, object param, IDbTransaction transaction, int? commandTimeout, CommandType? commandType)
{
var identity = new Identity(sql, commandType, cnn, typeof(T), param == null ? null : param.GetType(), null);
var info = GetCacheInfo(identity);
using (var cmd = SetupCommand(cnn, transaction, sql, info.ParamReader, param, commandTimeout, commandType))
{
using (var reader = cmd.ExecuteReader())
{
Func<Func<IDataReader, object>> cacheDeserializer = () =>
{
info.Deserializer = GetDeserializer(typeof(T), reader, 0, -1, false);
SetQueryCache(identity, info);
return info.Deserializer;
};
if (info.Deserializer == null)
{
cacheDeserializer();
}
var deserializer = info.Deserializer;
while (reader.Read())
{
object next;
try
{
next = deserializer(reader);
}
catch (DataException)
{
// give it another shot, in case the underlying schema changed
deserializer = cacheDeserializer();
next = deserializer(reader);
}
yield return (T)next;
}
}
}
... see it there in the nested using code? I wonder if due to the yield return (T)next; code inside the while, inside the nested using, if that is causing an issue.
The thing is that with a moderate amount of traffic, Dapper seems to operate just fine. However in a system with about 1000 requests per second, it seems to trip up.
I guess this is more of a FYI for the Dapper dev's, and wondering if they could resolve this.
(and I realize I miss-named DapperORM in the code - it's not an ORM)
You only read the first row of the datareader, so it never gets closed if there is more than one row.
A bit late to the party but it might help someone that will get stuck as me.
The issue is that Dapper "Query" method returned IEnumerable that is actually using a "yield return" statement to generate an iterator to the result set:
// From Dapper SqlMapper.cs QueryImpl function:
while (reader.Read())
{
object val = func(reader);
if (val == null || val is T)
{
yield return (T)val;
}
else
{
yield return (T)Convert.ChangeType(val, convertToType, CultureInfo.InvariantCulture);
}
}
The part that closes the DataReader happens later.
So in case you won't iterate over the entire result set and try to query another request you will get the "There is already an open DataReader associated with this Command which must be closed first" error.
I used Entity Framework to generate my classes, so and created a different repository for DAL access - rather than using Dapper, I simply rewrote the access code to use Entity Framework. Nothing different than the EF connection strings and using the EF database context in my using statements.
It all works just fine.
From what I read, Dapper is pretty fast, which is why I initially chose this for my DAL. However, it seems it has its limitations in a high frequency transaction environment. Maybe the Dapper team can clarify this in case I missed something or implemented something incorrectly.
The answer from Ladislav Mrnka on a similar question makes more sense:
This can happen if you execute a query while iterating over the results from another query...
One thing that can cause this is lazy loading triggered when iterating over the results of some query.
This can be easily solved by allowing MARS in your connection string. Add MultipleActiveResultSets=true to the provider part of your connection string (where Data Source, Initial Catalog, etc. are specified).
https://stackoverflow.com/a/6064422/1681490
More info on MARS here: http://msdn.microsoft.com/en-us/library/h32h3abf(v=vs.100).aspx
I have asked the same question at http://social.microsoft.com/Forums/en-US/crmdevelopment/thread/d5d00302-8f7b-4efc-873b-c54b3e29749d but didn't get an answer. So, I will give another try at stackoverflow.
I was running the example code from the crm 2011 training kit.
var creds = new ClientCredentials();
var dsp = new DiscoveryServiceProxy( dinfo, creds);
dsp.Authenticate();
var orgRequest = new RetrieveOrganizationRequest();
var response = dsp.Execute(orgRequest);
var orgResponse = response as RetrieveOrganizationsResponse;
if (orgResponse != null)
comboOrgs.ItemsSource = orgResponse.Details;
At the line of var response = dsp.Execute(orgRequest), I got the FaltException`1, the detailed message is as follows
System.ServiceModel.FaultException`1 was unhandled
Message=organizationName
Source=mscorlib
Action=http://schemas.microsoft.com/xrm/2011/Contracts/Discovery/IDiscoveryService/ExecuteDiscoveryServiceFaultFault
StackTrace:
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
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 Microsoft.Xrm.Sdk.Discovery.IDiscoveryService.Execute(DiscoveryRequest request)
at Microsoft.Xrm.Sdk.Client.DiscoveryServiceProxy.Execute(DiscoveryRequest request)
I was able to access the Discovery.svc file using browser. So the server url should be correct. Is this an authentication problem?
Is this for Microsoft CRM Online or on-premise? For Online, I know you would want to use something along the lines of what is found in the SDK -
// Connect to the Discovery service.
// The using statement assures that the service proxy will be properly disposed.
using (DiscoveryServiceProxy _serviceProxy = new DiscoveryServiceProxy(serverConfig.DiscoveryUri,
serverConfig.HomeRealmUri,
serverConfig.Credentials,
serverConfig.DeviceCredentials))
{
// You can choose to use the interface instead of the proxy.
IDiscoveryService service = _serviceProxy;
#region RetrieveOrganizations Message
// Retrieve details about all organizations discoverable via the
// Discovery service.
RetrieveOrganizationsRequest orgsRequest =
new RetrieveOrganizationsRequest()
{
AccessType = EndpointAccessType.Default,
Release = OrganizationRelease.Current
};
RetrieveOrganizationsResponse organizations =
(RetrieveOrganizationsResponse)service.Execute(orgsRequest);
}
There are overloads for the DiscoveryServiceProxy class but if you provide some more details on what you are trying to connect to, I think it will narrow it down.
I am using the new WCF-SAP adapter with BizTalk 2013.This adapter gives the option to use the classic RFCSdk or the SAP .net connector. My SAP Receive location works fine with the classic RFCSdk connector type but when I change it to NCo my receive location doesn't enable. I receive the following error in the Application log when I try to enable it after restarting the Host instance
The Messaging Engine failed to add a receive location "WcfReceiveLocation_SAPBinding_IdocDEBMAS05V3R740_Custom" with URL "**sap://CLIENT=300;LANG=EN;#a/sv-sapecc-dv2/00?GWHOST=sv-sapecc-dv2&GWSERV=sapgw00&ListenerDest=BIZTALKDEV&ListenerGwServ=sapgw00&ListenerGwHost=sv-sapecc-dv2&ListenerProgramId=BIZTALKDEV&RfcSdkTrace=True&AbapDebug=False**" to the adapter "WCF-Custom". Reason: "System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Adapters.SAP.NCo.RfcServerConnection.GetParameters(String serverName)
at SAP.Middleware.Connector.RfcServerManager.GetServer(String serverName, Type[] rfcFunctionHandlers, RfcRepository repository)
at Microsoft.Adapters.SAP.NCo.RfcServerConnection.Open(RfcClientConnection conn)
at Microsoft.Adapters.SAP.SAPInboundContract.InitializeRfcServerConnectionNCo(String connectionArguments)
at Microsoft.Adapters.SAP.SAPInboundContract.StartListener(String[] listenerActions, TimeSpan timeout)
at Microsoft.ServiceModel.Channels.Common.Channels.AdapterChannelListener`1.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)".
On the second Try I get the following Error
The Messaging Engine failed to add a receive location "WcfReceiveLocation_SAPBinding_IdocDEBMAS05V3R740_Custom" with URL "sap://CLIENT=300;LANG=EN;#a/sv-sapecc-dv2/00?GWHOST=sv-sapecc-dv2&GWSERV=sapgw00&ListenerDest=BIZTALKDEV&ListenerGwServ=sapgw00&ListenerGwHost=sv-sapecc-dv2&ListenerProgramId=BIZTALKDEV&RfcSdkTrace=True&AbapDebug=True" to the adapter "WCF-Custom". Reason: "SAP.Middleware.Connector.RfcInvalidStateException: destination configuration already initialized
at SAP.Middleware.Connector.RfcDestinationManager.RegisterDestinationConfiguration(IDestinationConfiguration config)
at Microsoft.Adapters.SAP.NCo.RfcServerConnection.Open(RfcClientConnection conn)
at Microsoft.Adapters.SAP.SAPInboundContract.InitializeRfcServerConnectionNCo(String connectionArguments)
at Microsoft.Adapters.SAP.SAPInboundContract.StartListener(String[] listenerActions, TimeSpan timeout)
at Microsoft.ServiceModel.Channels.Common.Channels.AdapterChannelListener`1.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)".
Any help on how to resolve these errors?