You’re offline. This is a read only version of the page.
We have an older Dynamics GP user who had an employee make some changes to the stored procedures and now getting litany of issues when trying to run the conversion. Would anybody know what the following errors would point to?
Event Type: Error
Event Source: SQLISPackage100
Event Category: None
Event ID: 12550
Date: 7/31/2015
Time: 10:54:21 AM
User: NT AUTHORITY\SYSTEM
Computer: ABRAHAM
Description:
Event Name: OnError
Message: The StoredProcedure '[dbo].[eConnectOutCreate]' cannot be scripted as its data is not accessible.
StackTrace: at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(DependencyCollection depList, SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Scripter.EnumScriptWithList(SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Transfer.Microsoft.SqlServer.Management.Common.ITransferMetadataProvider.SaveMetadata()
at Microsoft.SqlServer.Management.Dts.DtsTransferProvider.Configure(ITransferMetadataProvider metadataProvider)
at Microsoft.SqlServer.Management.Smo.Transfer.GetTransferProvider()
at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Property TextHeader is not available for StoredProcedure '[dbo].[eConnectOutCreate]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. The text is encrypted.
StackTrace: at Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.GetTextProperty(String requestingProperty, ScriptingOptions so, Boolean bThrowIfCreating)
at Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.BuildText(ScriptingOptions so)
at Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase.GetTextForScript(ScriptingOptions so, Boolean forCreate, String[] expectedObjectTypes, Boolean forceCheckNameAndManipulateIfRequired)
at Microsoft.SqlServer.Management.Smo.StoredProcedure.ScriptInternal(StringCollection queries, ScriptingOptions so, Boolean bForCreate)
at Microsoft.SqlServer.Management.Smo.StoredProcedure.ScriptSP(StringCollection queries, ScriptingOptions so, Boolean bForCreate)
at Microsoft.SqlServer.Management.Smo.StoredProcedure.ScriptCreate(StringCollection queries, ScriptingOptions so)
at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithListWorker(DependencyCollection depList, SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(DependencyCollection depList, SqlSmoObject[] objects)
*This post is locked for comments
I have the same question (0)
Hi Henry -
What version of Dynamics GP are you currently using?
What stored procedures were modified and what were they modified to do? You could always drop and recreate the stored procedures to get through the conversion, but it would help to know what they were supposed to do.
--Sean
Share
Report
All responses (
Answers (
1