Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepository'dbo.grmGetRepositoryCategories' doesn't exist
Previous
 
Next
New Post
11/5/2008 6:05 PM
 
Repository module. Latest version.

If I try and acess a page with the module installed, I get:
A critical error has occurred.
The stored procedure 'dbo.grmGetRepositoryCategories' doesn't exist.
But I can at least display the page.

As the host admin I try to set the settings on the page with the module and it throws an error. The log shows:

ModuleId: 454
ModuleDefId: 145
FriendlyName: test
ModuleControlSource: DesktopModules/Repository/Repository.ascx
AssemblyVersion: 04.08.00
PortalID: 0
PortalName: Espey Intranet
UserID: 1
UserName: web-admin
ActiveTabID: 60
ActiveTabName: Test
RawURL: /DotNetNuke/Default.aspx?tabid=60&ctl=Module&ModuleId=454
AbsoluteURL: /DotNetNuke/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 93c48de6-f5f3-49bb-a571-ee07e2d486a3
InnerException: The stored procedure 'dbo.grmGetRepositoryCategories' doesn't exist.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlCommand.DeriveParameters
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The stored procedure 'dbo.grmGetRepositoryCategories' doesn't exist. ---> System.InvalidOperationException: The stored procedure 'dbo.grmGetRepositoryCategories' doesn't exist. at System.Data.SqlClient.SqlCommand.DeriveParameters() at System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Repository.SqlDataProvider.GetRepositoryCategories(Int32 ModuleID, Int32 RootID) at DotNetNuke.Modules.Repository.RepositoryCategoryController.GetRepositoryCategories(Int32 ModuleId, Int32 RootID) at DotNetNuke.Modules.Repository.Settings.BindCategoryList(Int32 root) at DotNetNuke.Modules.Repository.Settings.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name: SERVER8

I've used MS SQL Server Management Studio Express to confirm the tables and stored procedures are in the db.

It LOOKS like this is a "legacy" module and it is using the legacy part of the web.config while the db was installed in the connectionstrings location. I tried aligning the two locations within the web.config, but they system won't let both instances open the db file at the same time...

Should I just not be running this module on 4.x?
 
New Post
11/5/2008 10:09 PM
 

the module works just fine with 4.X.   I know you say you checked the connection strings in your web.config, but I would check again. Many, many people are running the module under 4.X without any issues.

SQL Server? or SQL Express?  maybe you can post your connection strings ( * without the id and password of course ).  If you've verified manually that the stored proc is there, then it must be the connection string.

 
New Post
11/6/2008 9:07 AM
 
Thanx for the reply;
SQL Express 2005. I confirmed the version in the DB.

connectionStrings
add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Initial Catalog=DotNetNuke;Database=DotNetNuke;Integrated Security=True;" providerName="System.Data.SqlClient"

appSettings
add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;Database=DotNetNuke;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"

I've tried many variations on the second string with either the same results or with other modules failing, such as the Links module.
 
New Post
11/6/2008 10:03 AM
 

SQL Express can be tricky if you are using it for DNN AND also open the same database file using SQL Express Management Studio. Check this post out and see if it helps.

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1202/DNN-SQLExpress-SQL-Server-Management-Studio.aspx

 

 
New Post
11/6/2008 11:21 AM
 

SWEET!!!
I was able to perform the steps on my active DNN db through the Manager without having to scrap or rename anything.
Made the follwing edit only to the appSettings:

Before:
add key="SiteSqlServer"
value="Data Source=.\SQLExpress;
Integrated Security=True;
Database=DotNetNuke;
User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"


After:
add key="SiteSqlServer"
value="Data Source=.\SQLExpress;
Integrated Security=True;
Database=DotNetNuke;
User Instance=False"

The Repository module is now functioning.

Thanx for the help!

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepository'dbo.grmGetRepositoryCategories' doesn't exist


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out