About audrey

audrey · ‎07-20-2021

Hi Boštjan, I would try to set MAX_ERROR_COUNT to 0 on the node that shows this error. It might return an INSERT error that will help you understand what's actually wrong. Hope this helps. Audrey

audrey · ‎07-08-2021

Hi, Here's something you can try: - in your first Data Job, read the lines and count how many you have in an Expression node. User setvar function to save this in a Process Job variable. Write all records to a Worktable. - use the Global Get/Set node to set an increment counter value to -1 - use the Global Get/Set node to add 1 to this value - use the If Then node to test if this counter is less than the total number of records - if yes, read a line from the Worktable and call a Data Job that reads your input file (Contract_%%ContractNo%%.txt) and writes to the output. - connect this Data Job back to the Global Get/Set node that increments the counter. I am attaching a zipped version of a test job you can use. Hope this helps. Audrey

audrey · ‎07-06-2021

Hi, Your screenshot shows the error happen on the Data Target (Insert) node. This node has a parameter that allows it to ignore a certain number of errors before it actually fails. This number is set to 500 in your job. That means, the job ignored 499 insert errors, but when reaching 500, which is the maximum it is allowed to ignore, it failed. You might want to check in your database log what these errors are. If it's ok for your job to ignore it, you can set the MAX_ERROR_COUNT value to something higher than 500. If not, you can set it to 0 so it fails at the very first error. Hope this helps. Audrey

audrey · ‎06-03-2021

I don't think these errors are related to the crash you describe. Can you open a case with Tech Support? support@sas.com Thanks, Audrey

audrey · ‎06-03-2021

Hi, Do you see anything in the Data Management Studio log? It should be in C:\Users\{userName}\AppData\Roaming\DataFlux\DMStudio\{instanceName} Thanks, Audrey

audrey · ‎05-31-2021

The logs in DMStudio\2.8\Logs are the Data Management Studio logs (= the client log). The error message you get seem to indicate a problem on the SAS Business Data Network side. The logs for this app should be (by default) under config\Lev1\Web\Logs\SASServer13_1.

audrey · ‎05-31-2021

Hi, There might be a bit more information in the SAS Business Data Netwok log file. Can you check there if any error message is written? Thanks, Audrey

audrey · ‎05-31-2021

Hi, In Data Management Studio, you can use the Parsing node (under Quality) with the Address (Full) definition. This requires a Quality Knowledge Base. https://support.sas.com/downloads/browse.htm?fil=&cat=540 Hope this helps. Audrey

audrey · ‎05-10-2021

Hi, This could indicate that the repository in which you stored your rules can't be accessed from this new environment. Is this using Data Management Studio or Server? What kind of repository did you use? Is it stored in a database? If so, can you make sure the Data Connection is working properly and the credentials for it are saved? Can you attache the job you're trying to run here? Thanks, Audrey

audrey · ‎04-28-2021

There are 2 things I can think of: permissions and mapping of the Z: drive. If none of this helps, I'd suggest to open a Tech Suppor track providing these screenshots and the platfom logs from both environments. Audrey

audrey · ‎04-28-2021

Can you show what it looks like from a working environment? Can you also show the Administration > Repository definition for both?

audrey · ‎04-28-2021

Hi, I am assuming they see the repository itself in the Folders riser, right? Then, when they unfold it, do they see any folder? Do they see any jobs, or none? What type of jobs are stored in the reposiroty: profile jobs, data jobs, process jobs? Thanks, Audrey

audrey · ‎04-09-2021

Can you give a little more details about your job? What nodes do you use, what data do you read, how long does it take to run? Thanks. Audrey

audrey · ‎04-08-2021

Hi, There might be 2 things you can use: - Previewing the node which can be done by Right-click > Preview (also use F6) - Changing the MAX_OUTPUT_ROWS for your Input node: this will reduce the records read from the input database Hope this helps. Audrey

audrey · ‎04-02-2021

Hi, This could be related to accessing the databa&se, but I'm not sure to have enough information to help. Would you be able to open a ticket with Technical Support and provide the job and log file? https://support.sas.com/en/technical-support/contact-sas.html Thanks, Audrey

Online Status	Offline
Date Last Visited	‎08-29-2025 09:41 AM