Free Support Forum - aspose.cloud

SQL Server Errors appearing in Word Conversion


#1

We are experiencing lot of failures while using Aspose Words Cloud.
We are seeing lot of errors related to SQL Server, can you please have a look at this on priority

Here’s a sample error we are getting

 AppSID: 614b37e7-5811-41ba-b9a6-a5d00d7c1cb0, Version: API:1;PRODUCT:19.1.0.0;PRODUCT_CLOUD:19.1.0.0;, Method: UpdateSectionPageSetup. Previous exception: -------INNER EXCEPTION----------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Inner Exception type: SqlException
Inner Exception Stacktrace:
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
-----------INNER EXCEPTION------------
-------INNER INNER EXCEPTION----------
Msg:The network path was not found
Inner Inner Exception type: Win32Exception
Inner Inner Exception Stacktrace:

-----------INNER EXCEPTION------------
The underlying provider failed on Open.
Exception type:EntityException
Stacktrace:
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
   at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
   at Dynabic.Platform.Services.Users.UserService.<>c__DisplayClass7_0.<GetAppsUser>b__0() in c:\builds\aspose.cloud\platform.legacy\api-prod\src\Libraries\Dynabic.Platform.Services\Users\UserService.cs:line 331
   at Dynabic.Platform.Services.Caching.RedisCacheClient.Get[T](String key, Func`1 func, Nullable`1 cacheLifeTimeMinutes) in c:\builds\aspose.cloud\platform.legacy\api-prod\src\Libraries\Dynabic.Platform.Services\Caching\RedisCacheClient.cs:line 219
   at Dynabic.Platform.Services.Users.UserService.GetAppsUser(String appSid, Boolean withPropertiesFromPassport) in c:\builds\aspose.cloud\platform.legacy\api-prod\src\Libraries\Dynabic.Platform.Services\Users\UserService.cs:line 327
   at Dynabic.Platform.RestApi.Base.Filters.AFilter.InitializeCommonProperties(HttpActionContext ctx, App& app, String& ipAddress, String& assemblyVersions, String& serviceName, Method& method, User& user, AccountSubscription& accountSubscription) in c:\builds\aspose.cloud\platform.legacy\api-prod\src\Api\Dynabic.Platform.RestApi.Base\Filters\AFilter.cs:line 91

Please look into this on priority

Thanks
Abhishek


#2

@RBIEGTechTeam

We are sorry for your inconvenience. We have investigated the issue and found the root cause. It is not a bug in aspose.words cloud API but something in the AWS environment that effecting intermittently the API calls. We are working on it as high priority and will notify you as soon as it is resolved.


#3

We are also getting this error. The UTC+02 timestamp it happened for us was 5/28/2019 04:13

Can we get an update on the fix for this problem?

Is this an exception that can get solved by retrying?


#4

@rvanlaak

Thanks for your inquiry. Above error seems some network related issue. However, can you please share your error details(message). It will help us to identify whether it is same error or different.

We are sorry for your inconvenience.


#5

We do not have more information, the error message is almost identical.

Can you give an update on the fix for the AWS problems mentioned on February 27?


#6

@rvanlaak,

We had memory issues with big files and made some load balancing changes on the server. We are unable to notice this issue after this fix.

Furthermore, along with the load balancing update, we have also deployed a new fix to route requests larger than 5MB to another server for processing. So we are confident you will not face this issue again. Thanks for your understanding.


#7

We did not see any more SQL server outputs in the logs on the last 100 conversion errors, so this seems resolved.