.NET Runtime failure initializing profiling API (event ID 1022) - KiXtart.org - official site

You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Basic Scripting » .NET Runtime failure initializing profiling API (event ID 1022)

Page 1 of 1

1

Topic Options

#212038 - 2016-10-19 09:29 PM .NET Runtime failure initializing profiling API (event ID 1022)
RWebster7 RWebster7 Just in Town Registered: 2016-10-19 Posts: 2 Loc: Texas	Hello, I know nothing about kixtart, but have an issue on a MS SQL server where I see these errors every hour: .NET Runtime version 4.0.30319.34014 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005. Process ID (decimal): 16376. Message ID: [0x2509]. Having no idea where these were coming from, I used process monitor to capture the details and trace this so I could find out what the "Process ID" was related to. It came back to wkix32.exe running. There were 12000+ operations captured, and I cannot see anything glaring in the information that points me to the problem. Did several google searches but cannot find anything relevant. There are many "Success" operations and quite a few where "NAME NOT FOUND" and "PATH NOT FOUND" show up. This is on Windows Server 2012 R2 (x64) SQL Server 2014 SP2 Any help would be greatly appreciated.
Top

#212040 - 2016-10-19 11:42 PM Re: .NET Runtime failure initializing profiling API (event ID 1022) [Re: RWebster7]
Glenn Barnas Glenn Barnas KiX Supporter Registered: 2003-01-28 Posts: 4401 Loc: New Jersey	Welcome to KORG! This could be just about anything, so to narrow it down, here's a little overview: Kixtart began life as an advanced login script processor and has evolved into a powerful administrative scripting tool. WKIX32 is the "windowing" version of Kixtart - it is used to run Kix scripts that don't output to a console device/window. It's most commonly used to create system services, background automation, and GUI-based tools. The standard Kixtart file extensions are .KIX and .KX, the latter being the default for tokenized scripts (semi-compiled, non-readable). I'd start by searching your server for all the .KIX files. If you've ever programmed in BASIC or VB, it should be quite understandable. You can post the scripts here and we can help you figure out what they are doing, and hopefully, what's going wrong. The most common issue with admin scripts is an app upgrade that causes paths or app names to change. Review any of the scripts you find and obfuscate any potentially proprietary info (credentials, public server names, etc.) before posting. Put the scripts between CODE tags (a "[", the word "code" and a "]" - the end tag is "/code") and it will retain the format/indent and even colorize the script. Hope that gets you started! Glenn _________________________ Actually I am a Rocket Scientist! $\:D$
Top

#212048 - 2016-10-20 04:36 PM Re: .NET Runtime failure initializing profiling API (event ID 1022) [Re: Glenn Barnas]
RWebster7 RWebster7 Just in Town Registered: 2016-10-19 Posts: 2 Loc: Texas	Thanks for the insight. I noticed yesterday that there were wide gaps in the logs when this would run, I also found that the actual command was running from the "temp" folder under my profile. The gaps are because this is something that apparently runs when a login is made through RDP and then continues to run every hour while that user remained logged in. I can see now that it must be something in the script itself, and I forwarded the information to our systems team to get some insight into the script itself and why it might be causing these errors. Edited by RWebster7 (2016-10-20 04:36 PM)
Top

Page 1 of 1

1

Previous Topic

Previous Topic View All Topics

View All Topics

Index Next Topic

Next Topic

Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart

Hop to:

Shout Box

Who's Online

0 registered and 601 anonymous users online.

Newest Members

M_Moore, BeeEm, min_seow, Audio, Hoschi
17883 Registered Users

Generated in 0.047 seconds in which 0.023 seconds were spent on a total of 13 queries. Zlib compression enabled.

click tracking