Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!

Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!

Check out this thread to learn more!

Interaction between Windows Scheduler and OA Integration Manager when running user is not logged in

edited Dec 3, 2019 2:43PM in General

I have opened a case for this, but NetSuite does not seem to think that their recent changes regarding encryption can be what is causing the problem.  I am posting here to see if anyone else has run into this issue.

For several months now, I have been running an overnight batch using Windows Scheduler.  Part of the batch process runs shortcuts of OA Integration Manager (IM from now on).  All other parts of the batch process (hitting an internal system/database, and also running SalesForce Data Loader from the command line) continue to work fine. 

Last Tuesday night (7/19), the OA IM processes failed to export any data.  The process starts, but the CSVConnector never connects.  I have tracked down the issue to whether or not the user running Windows Scheduler is logged into the box where the process is being kicked off.  The Windows scheduler has ALWAYS been set to run whether the user is logged on or not.  And it has always run without a problem.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 3 (Jul-Sep 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders