Why is the topic I'm trying to start not posting?

  • I have a very challenging issue with integrating a CLR on a new MSSQL17 server i'm migrating to.  I've written a very detailed topic regarding the issue seeking expert advise from the members here, but for some reason my topic never shows up.  I was trying to post it in the SQL Server 2017 - Development category, as this issue seems to be more related with MSSQL 2017 rather than the CLR Assembly itself.  I tried reposting the topic today and saw it on the forum for a skinny minute, then when I tried to post an edit to the topic (a code block didn't post correctly originally) I got a notification that the topic had been flagged as spam and removed.  really could use expert help on this topic.  How can I get it posted?

    Thanks!

    John

  • I was able to post it on the ASK SCC forum, but would also like to get it going here as well, as these forums seem to be separate entities.

    https://ask.sqlservercentral.com/questions/156799/issue-with-mssql-2017-clr-referencing-ibmmq-amqmdn.html

     

  • Not sure why, but I've unmarked this so it shows up.

  • Steve, you rock sir!  Thank you!  Now to see if anyone can give me a clue how to solve this (or if its truly a compatibility bug.)  🙂

  • I have no idea, but I'll reach out to a few people

  • Thanks!  I seem to have another issue with the new topic however.  On my browser (chrome) the first code block that should have the stack track is showing blank on the main post.  If i click edit, it shows the content in the editor.  any ideas why it's doing that?  I'm going to try to drop in this topic and see if it does the same thing...

    Stack trace:

    Msg 6522, Level 16, State 1, Procedure sp_clr_MQ_SimplePut, Line 0 [Batch Start Line 25]
    A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_clr_MQ_SimplePut":
    System.TypeInitializationException: The type initializer for 'IBM.WMQ.MQQueueManager' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentException: The path is not of a legal form.
    System.ArgumentException:
    at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
    at System.IO.Path.InternalGetDirectoryName(String path)
    at IBM.WMQ.ManagedCommonServices..ctor()
    System.Reflection.TargetInvocationException:
    at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
    at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    at System.Activator.CreateInstance(Type type, Boolean nonPublic)
    at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
    at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
    at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
    at IBM.WMQ.CommonServices.CreateCommonServices()
    at IBM.WMQ.CommonServices.TraceConstructor(String objectId, String sccsid)
    at IBM.WMQ.Nmqi.NmqiEnvironment..ctor(NmqiPropertyHandler nmqiPropertyHandler)
    ...
    System.TypeInitializationException:
    at IBM.WMQ.MQQueueManager..ct...
  • Yep, did it here too.  must be some combination of characters in the trace itself causing the block to not render correctly?

  • Probably. There are various items used for markup, so if one of those is i the stack trace, it could cause issues. best to just add to the thread rather than edit the trace.

  • ok, cool.  Thanks a again for the quick response!

  • Hi John. I did see your post on Ask.SSC and was about to post something there.

    Regarding posting the question here in the "SQLCLR" forum/topic vs the "SQL Server 2017 - Development" forum: SQLCLR is kind of a thing unto itself, so it's best to post anything SQLCLR related into the SQLCLR forum and mention was version you are on. Can either you or Steve please move your post here on the SSC forums to the SQLCLR topic? Thanks!

     

    Take care,

    Solomon...

     

    SQL#https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
    Sql Quantum Lifthttps://SqlQuantumLift.com/ ( company )
    Sql Quantum Leaphttps://SqlQuantumLeap.com/ ( blog )
    Info sitesCollations     •     Module Signing     •     SQLCLR

  • Solomon, thank you for your response.  I think I was able to move my post to the CLR forum.  Thanks for the tip!

    John

  • Steve, just as info, it seems that my code block display issue was related to having the "Experimental Code Highlighting" turned on in my profile.  Turning it off allowed the code block to display as expected.  Just in case it was bugging you...  😉

    Thanks,

    John

  • Just FYI, the forum post in question is:

     

    https://www.sqlservercentral.com/forums/topic/issue-with-mssql-2017-clr-referencing-ibm-mq-amqmdnetstd-dll-3

     

    Take care, Solomon..

    SQL#https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
    Sql Quantum Lifthttps://SqlQuantumLift.com/ ( company )
    Sql Quantum Leaphttps://SqlQuantumLeap.com/ ( blog )
    Info sitesCollations     •     Module Signing     •     SQLCLR

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply