BTerrell Group Blog

Kevin Yu

Recent Posts

Resolving Windows Installer Coordinator on Terminal Server Issue

Posted by Kevin Yu on Thu, Sep 04, 2014


I installed Sage 300 ERP and Sage HRMS on a terminal server environment last week and was running into an issue with Windows Installer Coordinator. Often when I opened a UI, I would get a Windows Installer Coordinator popup that would run indefinitely. It actually prevented me from even running HRMS.

Windows installer coordinator

I found that there is a setting in Group Policy that disables Windows Installer Coordinator. I hope this helps if you run into this issue on a terminal server environment.





Windows Group lociy page







Windows Group Policy Editor







Edit compatiblity
Turn offWindows Installer

Tags: Sage 300 ERP, sage hrms, Windows

Gain productivity with the Right Accounting System

Posted by Kevin Yu on Tue, Sep 02, 2014

As your company grows, you can no longer rely on complicated, error-prone spreadsheets for reporting, or use extensive manual processes for accounting tasks. You may be ready to move to a new accounting system. The right accounting system can translate to significant productivity gains through automation of manual tasks, improved decision making with real-time reporting and visibility and a strong foundation to support your business growth.  Make sure you chose the right accounting system for your business.productive Intacct worker  

Download the Intacct whitepaper, Eight rules for investing in a new accounting system”, written by one of CPA Technology Advisor’s Top 25 Thought Leaders in Public Accounting, Geni Whitehouse and learn how you can operate more efficiently and effectively, improve your audit and control capabilities, easily comply with GAAP and IFRS accounting standards, and manage multiple entities and foreign currency.

I hope this whitepaper proves informative and provides some helpful insights. 

Tags: accounting system, Intacct

Sage Summit 2014 Recap

Posted by Kevin Yu on Tue, Aug 19, 2014

A few weeks ago, I had the opportunity to attend Sage Summit 2014, held at the Mandalay Bay in Las Vegas. With over 5200 attendees, this was by far the largest conference I have been to. I got to play with 3D printers and even work with Fixed Assets using Google Glass!Google Glass at Sage Summit

The keynote sessions were amazing. Jessica Alba, Magic Johnson, and Twitter co-founder Biz Stone were just some of the speakers in attendance. I also attended many of the Sage Intelligence breakout sessions and I was impressed by how much dedication Sage has put into adding value to the product. Sage Intelligence Go!, the new cloud reporting app, was highlighted during the first keynote as well as some of the sessions. The product utilizes Excel Online to allow users to address key business challenges and make mission-critical decisions anywhere, anytime.

Watch the keynote videos here!

Tags: business intelligence, BI, Sage Summit, Sage

Scheduled SQL Server Data Export to CSV using SQLCMD

Posted by Kevin Yu on Tue, Jun 24, 2014

You may recall my blog article last month about using the SQLCMD utility to run a script from the command prompt to restore a database. Ever since then, I’ve found more and more opportunities for the SQLCMD utility to help me manage challenges in Microsoft SQL Server.

This time, the challenge was to generate a scheduled CSV output of data from SQL Server. I could get the data I wanted formatted correctly by using a SQL query and then copy/paste into Excel, but I needed to find a way to have this process done automatically, on a schedule. A little bit of Google-ing led me back to utilizing the SQLCMD utility.

I saved my SQL query that returned the data formatted the way I needed and then entered the text below in the command prompt line:

sqlcmd -S server\instance -i  c:\SQL_Query.sql -o c:\CSV_Output.csv -s”,”

This generated the CSV file, but I still required this process to be scheduled. I knew I could use Windows Task Scheduler to start a program on a schedule I specified, and since SQLCMD is run from the command prompt (cmd.exe), I set up a task to start cmd.exe and used the above text in the add arguments field.

 6 24image1

I’ve included a list of other arguments for your reference you can pass sqlcmd:

   -a packet_size

   -A (dedicated administrator connection)

   -b (terminate batch job if there is an error)

   -c batch_terminator

   -C (trust the server certificate)

   -d db_name

   -e (echo input)

   -E (use trusted connection)

   -f codepage | i:codepage[,o:codepage] | o:codepage[,i:codepage]

   -h rows_per_header

   -H workstation_name

   -i input_file

   -I (enable quoted identifiers)

   -k[1 | 2] (remove or replace control characters)

   -K application_intent

   -l login_timeout

   -L[c] (list servers, optional clean output)

   -m error_level

   -M multisubnet_failover

   -N (encrypt connection)

   -o output_file

   -p[1] (print statistics, optional colon format)

   -P password

   -q "cmdline query"

   -Q "cmdline query" (and exit)

   -r[0 | 1] (msgs to stderr)

   -R (use client regional settings)

   -s col_separator

   -S [protocol:]server[\instance_name][,port]

   -t query_timeout

   -u (unicode output file)

   -U login_id

   -v var = "value"

   -V error_severity_level

   -w column_width

   -W (remove trailing spaces)

   -x (disable variable substitution)

   -X[1] (disable commands, startup script, environment variables and optional exit)

   -y variable_length_type_display_width

   -Y fixed_length_type_display_width

   -z new_password

   -Z new_password (and exit)


I set up my task to run every night at 2AM and it is working perfectly. The SQLCMD utility helped me resolve two challenges in the past month and I hope to find more opportunities to use SQLCMD to share moving forward.

Tags: SQL, Microsoft

SQL Server Troubleshooting: Collation Conflict

Posted by Kevin Yu on Tue, Jun 10, 2014


I was working on a project last week that required me to create a JOIN that links two tables in the same database. Typically this is a relatively simple process, but when I tried to execute my query, I got the following error message:

6 10image1





I was surprised to see this message since a single collation is usually used throughout a database. I checked the collation for each column in the tables by using the following query:

                SELECT, col.collation_name

                FROM sys.columns col

                WHERE object_id = OBJECT_ID(‘TableName’)

I found that the two tables I wanted to join were indeed using two different collation methods. In order to get around this issue, I forced which collation I wanted to use by using the COLLATE clause:

                SELECT *

                FROM Table1

                JOIN Table2

                ON Table1.ColumnA = Table2.ColumnA COLLATE SQL_Latin1_General_CP1_CI_AS

You can change either the first table’s collation method to match the second, or vice versa. You can also use COLLATE DATABASE_DEFAULT to use the default collation method set in the database properties.

I hope this will save you some time in the future when dealing with collation issues.


Tags: SQL, server, collate, collation