HomeHome Product Discus... Product Discus...SmithCartSmithCartUnable to manage ordersUnable to manage orders
Previous
 
Next
New Post
5/19/2014 3:24 PM
 
Hi Eric,

The reason I suggested a clean install is because it seems like you have limited access to your database which can make modifying stored procs difficult without SQL Server Management Studio access. It isn't required that you use the Clean Install Service to perform the clean install, just if you would like us to do the work for you.

This error you are receiving is being caused by an old Stored Procedure in your database that is referencing the function without your object qualifier. You can find all the Stored Procs referencing the fx_SmithGetPaymentTotalByOrderID function by running the following SQL script:

SELECT Name
FROM sys.procedures
WHERE OBJECT_DEFINITION(OBJECT_ID) LIKE '%SmithGetPaymentTotalByOrderID%'
GO

The above SQL script will give you a list of all Stored Procs in your database that reference the function. The following 3 Stored Procs are possibly referencing the fx_SmithGetPaymentTotalByOrderID without your Object Qualifier.

Smith_GetOrderCountByFilter
Smith_ListOrderByFilter
Smith_SA_ListCustomers

Once you locate the old Stored Proc without the object qualifier you can edit the Stored Proc, add your object qualifier, then run the Stored Proc and this should resolve the error.

Hope this helps!
 
New Post
5/20/2014 8:34 AM
 

I don't see anything on you site that says you MUST be a developer to use your module. Or that you can NOT just click the install button, then scroll through the install record to see that the module was installed successfully.

 

For a brand new site with a brand new "successful" install to have an "old stored procedure" that requires specialized software and training ... or pay for a clean install to resolve is unacceptable. I have a site with your module that has mini carts and category lists that do not work on the products detail pages; that has tokens that do not display; and has NO access to:

 

• Unable to access Manage Orders (A critical error has occurred. Cannot find either column “dbo” or the user-defined function or aggregate "dbo.fx_SmithGetPaymentTotalByOrderID", or the name is ambiguous.)

 

• Unable to access Ship Orders (A critical error has occurred. Cannot find either column “dbo” or the user-defined function or aggregate "dbo.fx_SmithGetPaymentTotalByOrderID", or the name is ambiguous.)

 
New Post
5/20/2014 12:00 PM
 
Eric,

Did you run the SQL script above to find which Stored Procs are not using the object qualifier? If you can provide me with the Stored Proc which doesn't have your object qualifier I can try to help you edit the Stored Proc.

I'd like to set up a phone call with you as well to discuss the issue on your site in more detail. Please submit a Help Desk ticket at the following link so we can schedule a call:http://www.smith-consulting.com/Suppo... 

It's important to test a new module before purchasing. While there are plenty of options for DNN, you want to make sure you are selecting the right software for you and your website. Not every module will be a good fit. 

It's also important to have a test environment when it comes to DNN where you can install new modules before doing it on your live site. This is especially true when you add SmithCart which now has 101 tables and 655 stored procedures. This moves your website into an ERP class app and in a lot of cases is mission critical to a business. If you don't have your own servers or your client doesn't have budget for another hosting account to setup another DNN instance you can create a DNN instance on your laptop or desktop computer as a test site. At the very least you should always have a full backup of your DNN install directory and database before installing new modules on a live site.

Thanks!
 
New Post
5/22/2014 5:37 PM
 
Update on this issue:

This error was not caused by an object qualifier, it was caused by the name of the Database Owner configured on the database. Typically the Database Owner is "dbo" but whoever set up your database changed it to "DotNetNuke_6" which is not good practice and can be dangerous. The database owner should always be "dbo".

.
 
Previous
 
Next
HomeHome Product Discus... Product Discus...SmithCartSmithCartUnable to manage ordersUnable to manage orders