Skip to content
+1-888-319-3663

COMMUNITY FORUM

SmartList Builder needs to finish installing

Jessica asked 5 years ago
After upgrading from GP 2010 to 2015 and updating SLB, each time we log in we’re getting the message that SLB needs to finish installing. Per an eOne blog post, we checked for Blank_Field_CB to be missing, but it was not. We’ve tried reinstalling, reregistering, but nothing works. Here is the end of the dexsql log up to the point of receiving the message, any suggestions?

/*  Date: 10/13/2016  Time: 12:18:12
stmt(166507248):*/
{CALL DYNAMICS.dbo.zDP_SY30000L_1(‘sa’,-32768,-2147483648,’sa’,32767,2147483647)}

/*  Date: 10/13/2016  Time: 12:18:12
stmt(166508152):*/
BEGIN DECLARE @stored_proc_name char(30) DECLARE @retstat int set nocount on SELECT @stored_proc_name = ‘DYNAMICS.dbo.smDEX_Clear_Locks’ EXEC @retstat = @stored_proc_name 4 SELECT @retstat set nocount on END
/*  Date: 10/13/2016  Time: 12:18:12
stmt(166368912):*/
delete from tempdb..DEX_SESSION where session_id = 4
/*
/*  Date: 10/13/2016  Time: 12:18:12
SQLSTATE:(S1010) Native Err:(0) stmt(0):*/
[Microsoft][ODBC Driver Manager] Function sequence error*/
/*
/*  Date: 10/13/2016  Time: 12:18:12
SQLSTATE:(00000) Native Err:(0) stmt(0):*/
*/
/*
/*  Date: 10/13/2016  Time: 12:18:12
SQLSTATE:(00000) Native Err:(0) status(18):*/
SWSTATUS DUMP*/
/*
/*  Date: 10/13/2016  Time: 12:19:22
SWSTATE:(SW041) Native Err:(41):*/
Number of results columns doesnt match table definition.*/
/*
/*  Date: 10/13/2016  Time: 12:24:42
SWSTATE:(SW041) Native Err:(41):*/
Number of results columns doesnt match table definition.*/
/*
/*  Date: 10/13/2016  Time: 12:37:03
SWSTATE:(SW041) Native Err:(41):*/
Number of results columns doesnt match table definition.*/
Justin replied 5 years ago

Was there ever a solution to this I am getting the same error?

Oleg replied 3 years ago

I have the same problem. How do we fix it?

Patrick Roth Staff replied 3 years ago

Running the Blank_Field_CB was a guess on Jessica’s part – it was clearly not the issue since wasn’t resolved by running that script.

Getting the Dexsql.log on her part is Step 1 of the solution – if you get generic error (which SLB is giving you), you have no idea the issue. You have to get that Dexsql.log to see the statement that failed and then the SQL error message.

From the original post of Jessica’s, she noted “Here is the end of the dexsql log up to the point of receiving the message”.

That statement is false. I know that because we see GP running smClear_Dex_Locks and deleting the DEX_SESSION record – that only happens as you log out of GP. So the “end” of the dexsql.log in this case isn’t useful.

So when you run your dexsql.log, log in as ‘non-sa’ user and get the message.
Leave it UP so that SLB doesn’t continue to process!
Review the dexsql.log, the statements should be at the bottom as Jessica tried to do.

And from there, you’d have to figure out how to fix whatever it is that is broken that SLB isn’t able to resolve.


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