What does this mean (exited with code 9009)

Hi All,

Error      1      The command "C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\\..\..\..\..\PostBuild.bat C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\\..\..\..\..\ C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\bin\Release\ HAT.DriveThruDetector" exited with code 9009.      HAT.DriveThruDetector

I do not understand what does the above error code mean. Because of this I am not able to compile my files. Please help me in resoloving the issue.

LVL 14
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Error code 9009 means your .bat file was not found. I think the post build command is launched using the output directory as working directory, so if your .bat file is located in the project directory, you have to use the relative path from the output directory back to the project directory.
Also take a look at this link

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
a) Does your program compile and run ok in debug build? If not then the error is a bug in your code and you should debug it with your debugger (Press F5 to run your program with the debugger)

b) Have you been writing build event scripts? If so it looks like your paths may not be correct. Try looking at the Build log (BuildLog.htm in your debug / release directory), and also check for any .InstallLog or .InstallState files and check them to see if they have any meaningful information in them.
sudhakar_koundinyaAuthor Commented:
Dear All,

Actuall problem is with my intermediate files. Once I deleted and rebuild the solution, it worked fine.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual C++.NET

From novice to tech pro — start learning today.