When trying to create a new order in the order entry screen and shipping product from inventory with a price of more than $0. If we check create invoice and attempt to post we get the following error:
Description: Incorrect procedure. Shipment cannot be posted. You must manually create the shipment from Shipment Entry.
Up until a server reboot earlier today this was not an issue and was our standard procedure.
Has anyone seen this before?
Does anyone have Office 365 and Doc Transmittal settings that work?
My client is planning to upgrade from MAS 500 v7.4.4 to v2014.1.
Can anyone offer pointers to best practices, checklists, installation and test procedures & plans. Plus, anything special to pay extra attention to?
Thanks in advance,
BruceB
Getting an error when launching Explorer - 'count' must be non-negative. Parameter name: count. I have rebuilt the view several times and am wondering if anyone has narrowed down what's going on with this error. I thought it might be bad data but maybe not... Any suggestions? Sage suggested rebuilding the view which I've now done several different ways... I've tried tracing it and it seems like it's not a SQL error.
Thanks John
Hello!
In Enter Sales Orders and Quotes, you can right-click the tranno, select Drill Into, and have a number of options available. (Quotes / Shipments / Invoices / Customers / Work Orders / Salesperson)
For one particular user, the Invoices option is not available. If I sign into Sage with a different user on the same computer, the option shows up.
How can I get the Invoices option to show as a Drill Into option when right-clicking the tranno in Enter Sales Orders and Quotes for this particular user?
Thank you.
Is there anywhere the GL account can be used for COGS except in Inventory Maintenance? I have issues on an Invoice Register that throws the COGS account into PPV and everything seems to be correct so I can't find where it is pulling from. Any help would be appreciated.
we switch Dbases for testing and each time we use the utility it comes up with a Client CPU name instead of the Server name.
Is there a way to change this so it will keep the server name?
Good day all!
Is there a way to prevent a dbase from showing up on the utility listing.
An example is StarShip has it's own Dbase yet you do not ever switch to it for Sage.
We also have several dbases the Server or other programs use but a client would never "Switch" to them for dbase utilization purposes.
I appreciate any assistance in this.
Hello
I have a user who is claiming the Invoices preview of the Explore Sales Order Task started running slow last Friday. I can confirm that preview option is running slow, while the other preview options all load relatively quickly. Nothing has changed around that task or the corresponding views recently.
A long while back we updated vdvInvoice by adding the following tables
left outer join dbo.tsoInvoiceShipment a on dbo.tarInvoice.InvcKey = a.InvcKey
left outer join dbo.tsoShipment b on a.ShipKey = b.ShipKey
left outer join dbo.tsoUPSInformation c on b.ShipKey = c.ShipKey
and the following fields:
, c.Cost, c.Handling, c.Published, dbo.tarCustomer.UserFld1 as 'Buying Group'
But this custom coding has been there since way before Friday.
In SQL Management Studio, Activity Monitor, Recent Expensive Queries, the vdvInvoice view query takes the top 3 spots when sorting by Average Duration.
Anything we can look at to figure out what's causing this decrease in performance?
We are purchasing finished goods from a partner company and would like to have a PO automatically closed for invoicing so we don't have to do it manually every purchase. Is there a way to do this?
Is anyone using StarShip version 15 or later and Sage 500 2014?
I'm wondering if anyone has the inside scoop on "System Batches" during upgrades.
Sometimes the upgrade procedure will stop and prompt you to deal with open "System Batches" resulting from open invoices, and other times it does not. I have seen inconsistency in this process. It would of course be better if it were consistent so that we could expect that what we will see when upgrading production systems would be the same behavior we saw during testing.
I'm trying to plan my upgrade from 7.4, which also has to include a server migration, OS upgrade to 2012R2, and a SQL Server upgrade.
Has anybody tested any version on SQL Server 2014?
I created a 7.4 blank db (except for COA, etc.) and migrated it over to a test instance on SQL Express, but all of the Server Utilities (DB Creation/Synchronization/Upgrade) fail on 2014.
Haven't purchased the licenses yet, but thought I'd poll the community. Obviously, I'd like to have the longest period of support on SQL Server as possible.
Unable to lock or delete fiscal year, 1900. Error Message - Fiscal Calendar: Record has been modified by another program.
I'm getting an error above metioned, even I tried to log to sample DB,
I got a message suddenly " you don't have license to use this product"
Then I tried to repair the accpac then I'm getting " You have reached maximum number of concurrent users for your lankpak "
We have Certificate Client ID it has 8 Digits, in the doc its syys 7 digit or 10 digit. can't understand.
FYI, windows update KB3102429 causes exporting to PDF to break.
https://support.microsoft.com/en-us/kb/3102429
Right now, uninstall KB3102429 and reboot the computer/server where Sage 500 is installed will provide a workaround.
Can somebody confirm this for me?
I'm working through test upgrades from 7.4.10 to the newly-released 2016 version. Our DB (before applying the 7.4 2015 1099 Update) upgrades successfully, but if the 1099 update is applied will fail during the 7.6->7.7 portion.
I then created a blank 7.4 DB and was able to replicate the issue on both sides: Successful w/o 1099, unsuccessful with 1099.
The DBERROR.LOG looks something like this (for the blank DB):
<snip>
Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.40\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.50 : 1/14/2016 4:05:08 PM
<snip>
END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.50 : 1/14/2016 5:01:31 PM
START TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:01:31 PM
END TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:01:31 PM
Loading dbmupd.sql to mas500Blank_app...
Loading dbmcomp.sql to mas500Blank_app...
BCPing pre-processed database information...
B Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\ColInfo.bcp
B Finish bcp of tdmTableColInfoP
C Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\IdxInfo.bcp
C Finish bcp of tdmTableIdxInfoP
D Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\ColInfo.bcp
D Finish bcp of tdmTableColInfoP
E Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\IdxInfo.bcp
E Finish bcp of tdmTableIdxInfoP
Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.50\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.60 : 1/14/2016 5:01:34 PM
<snip>
END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.60 : 1/14/2016 5:56:38 PM
START TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:56:38 PM
END TIME FOR CLEANING DATABASE: mas500Blank_app : 1/14/2016 5:56:38 PM
Loading dbmupd.sql to mas500Blank_app...
Loading dbmcomp.sql to mas500Blank_app...
BCPing pre-processed database information...
B Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\ColInfo.bcp
B Finish bcp of tdmTableColInfoP
C Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\IdxInfo.bcp
C Finish bcp of tdmTableIdxInfoP
D Start bcp of tdmTableColInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.70\ColInfo.bcp
D Finish bcp of tdmTableColInfoP
E Start bcp of tdmTableIdxInfoP C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.70\IdxInfo.bcp
E Finish bcp of tdmTableIdxInfoP
Loading C:\Program Files (x86)\Sage Software\Sage MAS 500 Database Utilities\DBUpgrade\7.60\all_app.lst to mas500Blank_app ...
START TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.70 : 1/14/2016 5:56:41 PM
<snip>
Upgrading tapV1099Box: -- Script for tapV1099Box: APP,Load Script Asynchronously - OK; 6:50:58 PM
Upgrading CM Multiple Offset Accounts Enhancement: -- Script for CM Multiple Offset Accounts Enhancement: cmzda001 (Enter Bank Transactions)Load Script Asynchronously - OK; 6:50:59 PM
Upgrading customization metadata: -- Script for customization metadata: APPLoad Script Asynchronously - OK; 6:51:00 PM
------>Upgrading Tax Year (TY) 2015 1099 User Data(PSC): -- Script for Tax Year (TY) 2015 1099 User Data(PSC): APP
Microsoft SQL Server Native Client 11.0 Error 3604:
Error occured while moving TY 2015 1099 User Data, PSC.
------>Upgrading Tax Year (TY) 2015 1099 User Data(PSC): -- Script for Tax Year (TY) 2015 1099 User Data(PSC): APP
Microsoft SQL Server Native Client 11.0 Error 3604:
Error occured while moving TY 2015 1099 User Data, PSC.Load Script Asynchronously - OK; 6:51:01 PM
------>Upgrading Tax Year (TY) 2015 1099 System Data(PSC): -- Script for Tax Year (TY) 2015 1099 System Data(PSC): APPLoad Script Asynchronously - OK; 6:51:02 PM
END TIME FOR UPGRADING DATABASE: mas500Blank_app to version 7.70 : 1/14/2016 6:51:02 PM
My client is using document transmittal for Invoices and their customers were having issues opening it. I have suggested that they remove the "Body Text" from the Set up Document Transmittal screen. This in turn alleviated a lot of the issues. Now they have noticed that sometimes when they send the invoice, the recipient in the "To" field cannot open the document (error below), but the recipient in the "CC" field can open it. They have also noticed that the size of the invoice attached to the recipient in the "To" field is slightly larger (about 40 KB) than the recipient in the "CC" field. Has anyone else seen this or know how to fix it?
I will start this off that I am using the tracker to review issues with a third party integration.
With that disclaimer, we are moving from 7.3 to 7.6 (cannot do 7.7 yet due to add-on). I am seeing that when we close most VB tasks (this one I used Maintain Items), the following string of errors display in the tracker feed.
10:25:42(5911 - 261012477)-UnloadSelf(Item Maintenance: ltContext 64)
10:25:42(1 - 261012478)-CheckUIActiveStateIncludingChild::"Item Maintenance" - GetlUIActive()
10:25:42(1 - 261012479)-"Item Maintenance" - GetlUIActive Failed, return value: 0
10:25:42(1 - 261012480)-UnloadObject::"Item Maintenance" - QueryShutdown(ltContext: 64)
10:25:42(2 - 261012482)-"UnloadObject" - UnloadUI(ltContext: 91161784)
10:25:42(2 - 261012484)-UnloadObject::"Item Maintenance" - TerminateObject(ltContext: 64)
10:25:42(2 - 261012486)-ReleaseSystemObject: Object not found.
10:25:42(2 - 261012488)-Caught Exception: "ReleaseSystemObject" - OLE Dispatch Error: m_scError:-2147175422(0x8004b402), Desc:ReleaseSystemObject: Object not found., Help:0, Help File-:: System Definition:
I just confirmed with another customer who has 7.6 running that they are seeing the same behavior. No known application issues.
I am a strong supporter of not ignoring errors even if they don't seem to be causing corruption or stop the user from performing a specific task.
Any feedback the community has would be appreciated.
Thank you all.
Has anyone experienced issues with this? We recently built out a new Citrix XAXD 7.6 environment on Win2012 servers and are receiving chronic reports of "Not Responding" messages from our test base both when launching tasks and trying to load reports.