Refine your search:

I'm running version 4.0.8 splunk on Windows 2000 and it continually generates the following error.

Application popup: splunk-regmon.exe - Entry Point Not Found : The procedure entry point GetProcessImageFileNameW could no be located in the dynamic link library PSAPI.DLL.

Event ID: 26 Source: Application Popup

asked 14 Apr '10, 01:36

mctester's gravatar image

mctester
6523324
accept rate: 75%

edited 14 Apr '10, 15:42

BunnyHop's gravatar image

BunnyHop
7254423


2 Answers:

1) Windows 2000 is not a supported platform. Splunk will run mostly just fine on it, but there's no guarantee everything will work 100%. Microsoft have already withdrawn genearl support for this OS

2) The 'regmon' script in the Windows app is causing the error. If you disable the regmon input in $SPLUNK_HOME/etc/apps/windows/default/inputs.conf, it will cease to bother you.

link

answered 14 Apr '10, 01:39

Mick's gravatar image

Mick ♦
4.0k1327
accept rate: 52%

We had this same problem in a test we were running in a customer environment. This post was a lot of help. However, we disabled the input in the .conf file in the directory above with no result. We found that this input is enabled by default, so we had to edit the inputs.conf under $SPLUNK_HOME/etc/system/default and change the regmon stanza to disabled=1.

link

answered 10 Jan '11, 08:31

gpburgett's gravatar image

gpburgett
936
accept rate: 33%

@gpgburgett: Did you disable the input in the ../local/inputs.conf file or simply remove it?
If you have the same stanza in multiple *.conf files, Splunk will layer them together and the settings in 'local' directories will be applied. If you had 'disabled=1' in a stanza with the same name in your ../local/inputs.conf, it should have killed the input for you. Strange that it didn't as this is basica functionality

(20 Jan '11, 00:38) mctester

We just disabled the input in the conf file. You're right, it should layer the conf files and apply them according to splunk's precedence rules. We've had this problem before though, especially on Windows, where Splunk doesn't recognize conf file changes right away, even after restart. If we had waited or tried restarting a few more times it probably would have worked. But in that case when we changed the default file, the change was applied right away.

(20 Jan '11, 18:20) gpburgett
Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×302
×220

Asked: 14 Apr '10, 01:36

Seen: 1,270 times

Last updated: 10 Jan '11, 08:31

Copyright © 2005-2012 Splunk, Inc. All rights reserved.