Control Issues Index
This page is the master “index” of WIKI articles for Control. The information is arranged in several formats. You may navigate using the Table of Contents on the right, or by typing Control-F and searching for specific text.
This organization of issues is arranged based on the Tier-designation used internally by Cyrious Software for their support technicians. A Tier-1 issue is well understood and the steps to repair it are straight forward. A Tier-2 issue is generally less common, presents differently in each case, or requires a high level of technical experience to resolve. A Tier-3 issue requires the most skilled technician applying the scientific method to diagnose and resolve the issue.
Tier 1 Issues
The following issues are generally Tier 1 issues. Tier 1 technicians should handle these issues as outlined in the steps detailed in the description. If the issue remains after the completion of the Tier 1 steps, the Tier 1 technician stops work on it and elevates the ticket to the next available Tier 2 technician.
Tier 2 Issues
- Problem is repeatable on the customer's system, or on multiple customer systems.
- Problem may or may not be recreated on another system
- Require an understanding in many areas such as database, data structure, reporting, pricing computation, etc.
- This type of problem requires a scientific method of hypothesis, research, and trial-and-error.
Inventory Home | Inventory Home | ||||||||
Inventory explanation: | Inventory Overview | ||||||||
How does Consignment Inventory Work? | Consignment Inventory (internal) | ||||||||
Adjusting Reserved levels (On Order) | Control SQL - Adjust Reserved Inventory Levels to Match Orders | ||||||||
Merge Duplicate Inventory Items | Merge Duplicate Inventory Items (SQL) | ||||||||
Merge Duplicate Inventory Summaries | Merge Duplicate Inventory Summaries (SQL) | ||||||||
Accounting | |||||||||
How to do a Retroactive Closeout | Retroactive Closeout | ||||||||
Which entries are made for accounting actions taken? | Accounting Reference Table (internal) GL Activity by Action (internal) | ||||||||
How do I post a payment for an order that was written off as bad debt? | How do I Post a Payment for an Order That Was a Write-Off to Bad Debt | ||||||||
How to handle an NSF Check and Update Quickbooks. | NSF Checks | ||||||||
How to repair Direct Cost from Bills. | Direct Cost from Bills Repair (billable) | ||||||||
How to process a refund in Quickbooks. | Refund in Quickbooks (internal) | ||||||||
How to check Order Tax settings. | Control - Order Tax Settings Lookup | ||||||||
How to insert a missing Journal (Activity) for Finance Charge on an Order | Insert Journal for Finance Charge (SQL) | ||||||||
How to Track Donations. | How To Track Donations | ||||||||
Part Usage | |||||||||
What is Smart Parts? | Smart Parts | ||||||||
Setup | |||||||||
* Adding Parts to OOB | Add Parts to OOB | ||||||||
* Setting up Data Importing | Importing Data home | ||||||||
Performance/Networking | |||||||||
* Troubleshooting O/S or Networking | General O.cyriouswiki.com/s_and_networking_home | ||||||||
* Cyrious Response to Virtualization | Virtual Machines (VM) and SQL Express (internal) | ||||||||
* Is the customer using virtualization? | How You Can Tell if the Server is a Virtual Machine or a Physical Machine | ||||||||
* Is my Anti-Virus causing problems? | Known Issues with Anti-virus Applications | ||||||||
SQL Optimization | |||||||||
Riot Creative Imaging - ARC | |||||||||
* Create a new Riot-ARC business location | Riot - ARC (new){internal} | ||||||||
SQL Server Related | |||||||||
* Determine SQL inconsistencies | SQL Master Reference - SQL HOME | ||||||||
* SQL Query home | Control SQL - Queries to Identify Problems | ||||||||
* Corrupted Database | SQL Server - DBCC_CHECKDB | ||||||||
* Clear SQL Processes without downtime | Control SQL - ODBC Process Removal Query | ||||||||
* Standard SQL Functions and Views | SQL Functions/Views (Standard with Control) | ||||||||
* Customize SQL Queries/Triggers (such as for Macros) | Modify Transaction Variable (Order Condition) | ||||||||
* Determine Control Version History | Control SQL - Version History | ||||||||
* Access Denied when attempting to log in | Access Denied When Attempting to Log Into SQL Management Studio | ||||||||
* Reinstall SQL Bridge | Control SQL -Reinstall SQL Bridge | ||||||||
Bug Submission | |||||||||
* Clearing customer info for bug testing on backup | Clear customer info for Testing (internal) | ||||||||
* Determine Recently Modified Records (SQL) | Control SQL - Recently Modified Records | ||||||||
* SQL Query to Search All Tables (TRAINING/TESTING ONLY) | This should not be run on a customer's system ever. | ||||||||
Unsupported Solutions | |||||||||
* Server Auto-Login | Auto Login User on Server (start Services) [Security Risk] |
Tier 3 Issues
* Tier 3 issues refer to problems with these characteristics:
* May not be easily defined.
* Are usually not easily repeatable
* Usually can't be [intentionally] recreated on another system
* Require a deep, broad understanding in many areas such as database, data structure, reporting, pricing computation, etc.
* May involve interaction with non-Control players or the operating system.
By their nature, there is not a list of Tier 3 issues. Rather this type of problem requires a sophisticated scientific method of hypothesis, research, and trial-and-error.
~ Customer Request or Error | ~ Tier 3 Action |
SQL Server | Preface - Some of the following topics will fall into Tier 3 due to the amount of data to be considered for the topic to be relevant. Pulling usage data, Profiling, and Tracing can involve VERY expensive queries that can or will impact or halt production on that database. These tasks will generally be required for companies with larger data-sets and considerations will be required to ensure that testing does not interfere with their production. |
||
* Database Corruption | SQL Recovery 1 SQL Recovery 2 - LDF lost/corrupted SQL Recovery 2.2 Attach MDF w/o LDF (sqlAuthority) |
||
* Copy Tables |
- This generates 1 index on the new table based on ID; Know the implications before utilizing this.||
* Track SQL Activities | Kill Tasks in SQL TSQL | ||
* Statistic Collection | Control - How to Determine the Size of Each SQL Database Table | ||
* Data-Set Modification | Merge Product Data-Set (SQL) | ||
* Data Extraction | Extract XML (SQL) | ||
* Performance Investigation/Tuning | ASYNC Network IO Waits (logicalread) | ||
By Subject
By Type of Error
Other Useful Information