Survey Forums

HomeHomeSurvey Project ...Survey Project ...Installation & ...Installation & ...MS SQL db errorMS SQL db error
Previous
 
Next
New Post
9/14/2017 2:30 PM
 
Hi,


I get this error everytm I try to build a db on MS SQL Management Studio 17 with SQL Express 16 on Windows 10 64bit. I just do as written in SP24 intallation manual (it is written there is no problem if all errors are white but I have a few red error below) but I couln't manage display my page on localhost. Please help, regards...


The module 'vts_spAnswerMatrixAddNew' depends on the missing object 'vts_spAnswerMatrixChildAddNew'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerMatrixUpdate' depends on the missing object 'vts_spMultiLanguageTextUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerTypeAddNew' depends on the missing object 'vts_spUserAnswerTypeAssignUser'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerTypeSetBuiltIn' depends on the missing object 'vts_spUserAnswerTypeUnAssignAllUser'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerUpdate' depends on the missing object 'vts_spMultiLanguageTextUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerUpdate' depends on the missing object 'vts_spMultiLanguageTextUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spAnswerUpdate' depends on the missing object 'vts_spMultiLanguageTextUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spFileAddNew' depends on the missing object 'vts_spFileDeleteExpired'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spFolderDelete' depends on the missing object 'vts_spSurveyDeleteByID'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionCloneByID' depends on the missing object 'vts_spQuestionSectionOptionClone'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionCloneByID' depends on the missing object 'vts_spQuestionGetDetails'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionCopy' depends on the missing object 'vts_spQuestionSectionOptionClone'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionCopyToLibrary' depends on the missing object 'vts_spQuestionSectionOptionClone'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionCopyToSurvey' depends on the missing object 'vts_spQuestionSectionOptionClone'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spQuestionGetResults' depends on the missing object 'vts_spVoterFilter'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spRegularExpressionAddNew' depends on the missing object 'vts_spUserRegularExpressionAssignUser'. The module will still be created; however, it cannot run successfully until the object exists.
Msg 137, Level 15, State 2, Procedure vts_spSurveyAddNew, Line 51 [Batch Start Line 9572]
Must declare the scalar variable "@folderid".
The module 'vts_spSurveyClone' depends on the missing object 'vts_spSurveySkipLogicRuleCopyToSurvey'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'vts_spSurveyClone' depends on the missing object 'vts_spSurveyGetDetails'. The module will still be created; however, it cannot run successfully until the object exists.
Msg 137, Level 15, State 2, Procedure vts_spSurveyGetListByTitle, Line 73 [Batch Start Line 11288]
Must declare the scalar variable "@userid".
Msg 137, Level 15, State 2, Procedure vts_spTreeNodesGetAll, Line 46 [Batch Start Line 13368]
Must declare the scalar variable "@userid".
Msg 137, Level 15, State 2, Procedure vts_spTreeNodesGetAll, Line 61 [Batch Start Line 13368]
Must declare the scalar variable "@userid".
The module 'vts_spVoterAddNew' depends on the missing object 'vts_spVoterUIdAddNew'. The module will still be created; however, it cannot run successfully until the object exists.

(1 row affected)

(1 row affected)

(1 row affected)

(1 row affected)"
 
New Post
9/14/2017 3:39 PM
 
Hi,

SP v. 2.4 is not developed and tested for MSsql 2016 databases. The DB scripts are for 2012 and 2014 databases (See installation guide).

Personally I ran the scripts on an 2016 database without any issues  hower it was in Management studio 2016. It may be that the Management studio 2017 + 2016 db makes certain new requirements that are not met by the 2012/ 2014 db scripts.

I cannot see what "red lines" are generated in your message but assume it has to do with:
Msg 137, Level 15, State 2, Procedure vts_spSurveyAddNew, Line 51 [Batch Start Line 9572]
Must declare the scalar variable "@folderid". and the other scalar related messages.

It will be investigated/tested  further in the next version of SP (v. 2.5). Untill then you can try and google the error messages and find a fix for the 2014 script.

If you have any other information just let me know.  Hope you get it fixed.

 
 
New Post
9/14/2017 8:27 PM
 
Thanks for quick respond. Yes, those "scalar" things are in red. I think I found a workaround. I just changed all;
"userid" to "UserID" and "folderid" to "FolderID" then MS2017 executed it without any red line.

Now, I can reach the frontpage but cant go further... It gives "provider: SQL Network Interfaces, error: 26".

Maybe it is related to WIN10, maybe not compatible with 2014db. I dont know but I'll try with MS16 and MS14 just like you said. I'll write more about the issue :)


Thanks, regards.
 
New Post
9/15/2017 2:42 PM
 
Hi again,


I followed the precedure again with SQLExpress and Studio 2014 on Win7 64bit. It fails again when it is executed.

Did the workaround I mentioned in upper post, then I get "500.19 0x800700b7" error. Followed the solution Microsoft suggested but there is no positive result. Problem is still here.


I'm so fed up with it, couldn't find any solution.
 
New Post
9/15/2017 5:15 PM
 
Hi,

Thank you for posting the additional information on the "scalar" issue. A 'capitals' issue really or so it seams. Remarkable and something to take care of in the next release.

Concerning the Sql network interfaces error. Check the following: 
https://blogs.msdn.microsoft.com/sql_protocols/2007/05/13/sql-network-interfaces-error-26-error-locating-serverinstance-specified/

It seems related to the name used to the sqlserver instance you'veinstalled. Also make sure you follow the exact instructions for the db connection setup in the SP web.config file. (Many mistakes are made there!).

Hope you get it fixed and keep us posted. Thanks again.
 
Previous
 
Next
HomeHomeSurvey Project ...Survey Project ...Installation & ...Installation & ...MS SQL db errorMS SQL db error