Skip to content
+1-888-319-3663

COMMUNITY FORUM

SmartList Builder Error Message – Logging On To GP

Vaidy asked 8 years ago
After we upgraded our SmartList Builder to 12.00.0056, we are getting the following error message:

Some features of SmartList Builder will be disabled until it is initialized by the system administrator.

What exactly is the setup that we are missing?
Jared replied 8 years ago

You need to log into GP using the 'sa' account and input the registration keys.

Answers
Best Answer
Vaidy answered 8 years ago
Hi Jared, thanks for the input and sorry for delayed response. Yes, I had to log on as SA and run the registration wizard again. Thanks again. Vaidy
Edgar Figueroa replied 7 years ago

[quote=Vaidy]After we upgraded our SmartList Builder to 12.00.0056, we are getting the following error message:

Some features of SmartList Builder will be disabled until it is initialized by the system administrator.

What exactly is the setup that we are missing?[/quote]

ArtCabot replied 7 years ago

[quote=Vaidy]After we upgraded our SmartList Builder to 12.00.0056, we are getting the following error message:

Some features of SmartList Builder will be disabled until it is initialized by the system administrator.

What exactly is the setup that we are missing?[/quote]

Jared answered 7 years ago
If you've logged in with the sa user and the sa user doesn't receive any messages you can run the grant.sql script or recreate the SmartList Builder views.  Neither option will do any harm and it's hard to know exactly what is going in without seeing the dexsql.log.  The grant.sql script can be found in the main GP install location-SQL-Util.  To recreate the views (logged in as sa) go to Microsoft Dynamics GP-Tools-Smartlist Builder-Maintenance-Create views.  Mark all the companies and click create.

If you still receive the message please send a dexsql.log to eOne Support.
Moideen answered 6 years ago
Iam receiving this message after installation and registration,
if I login as sa no issue, any other users not updating the smart list objects, please help.
Added  smart list recently,  purchased from e one for version 10.
 
 
Dynamics Gp version 10
SQL 2008 R2
Cory replied 6 years ago

Hello,

I’m getting the same error message and have tried all of the solutions above but am having zero luck with a GP2010 to GP2015 upgrade.

I’ve entered regkeys, ran grant, created views, etc.

If I give SQL sysadmin permissions the error goes away. In the SQL trace, and dex log I get a message about not being able to drop a procedure.

[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure ‘##zDP_1632722S_1’, because it does not exist or you do not have permission.*/

There area lot of messages similar to the one above.

Any ideas on this one?

Thanks!

Cory

Heidi Jensen replied 6 years ago

I am having the exact same issue as Cory. Upgrade from GP2010 to Gp2015. Sa has no issues but all other users receive the message that some features aren’t available. I have also recreated the views, run grant.sql, and even granted every company database access to all view in SLB security. Still no luck.
Help!

Jim Lines replied 6 years ago

Heidi,
I came across this post when I was searching yesterday and literally just fixed the problem after many many hours of work. I hope this helps you too!

Our problem appeared right after I installed the Project Accounting module.

I worked with Jared (thanks Jared) and together we were able figure out the problem. It appears SLB is counting the SLB Views (slbVendors, slbVendorAddresses, etc) that are found in each company database. If you do a dexsql.log up to the error message you will see where it’s doing the count. It looks something like this:

select count(*) FROM sys.views where name in (‘slbAccounts’,’slbCustomers’,’slbVendors’,’slbItems’,’slbEmployees’,’slbPayrollTrx’,…)

In our case when I ran that query, we came up with 78 slb views in our databases. However, when we (Jared) counted the views referenced in the dexsql.log, there were 79! I did the comparison by dumping the slb views from the dexsql.log and the query of slb views from one of our company databases into excel and found the missing one (slbVendors).

From there, I went on a hunt for slbVendors view. Fortunately I was able to find a backups pre-Project Accounting that still had the slbVendors view still in tact. I generated a Create Script and attempted to run it in on my production company database. HOWEVER, I received an error because the view was referencing a non-existing table (PA00001). Right away I knew what this was because it’s sister table (PA00002) had given me a problem before. Sparing the details, I had to create the PA00001 table in my company dbs and then was able to create the missing view and VIOLA! the error went away.

In summary, and I hope this works for you, actually count the number views in the dexsql.log and compare to the number that exist in the database. You said you upgraded and I’m wondering if maybe a table name change could be the cause.

Here’s some info:
–Run this on your company db to get the total number of SLB Views
select count (*)
from sys.views
where name like ‘slb%’

–Run this on your company db to get the names of all the SLB Views
select *
from sys.views
where name like ‘slb%’
order by name

The rest is copying and formatting in Excel. I hope this helps. 🙂

Happy Holidays,
Jim


If you would like to submit an answer or comment, please sign in to the eOne portal.