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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Moving from own system to Microsoft AzureMoving from own system to Microsoft Azure
Previous
 
Next
New Post
6/23/2014 4:27 AM
 

I have recently moved several websites from own hosting to Microsoft Azure.

If I try to add a new extension using the extension wizard I receive the following error message.

A critical error has occurred. Could not find stored procedure 'dbo.GetPackageType'.

Can you advise the best way to get the stored procedures working again properly as there seems to be either a permissions error or something similar.

It would be helpful if we could achieve this without rebuilding the website(s) completely.

 
New Post
6/23/2014 7:07 AM
 
if you check the database, is stored procedure GetPackageType present?
is it compiled?
Does the SQL server user being used have dnowner permission?
wich DNN version are you running?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/23/2014 11:29 AM
 

Most likely whatever account you have DNN accessing SQL with does not have Execute permission on the stored procedures in the database.  The account you're using should be a member of the dbowner role, because DNN has to change the schema for updates and so forth.

Check the connection string in web.config.  Find the account you're using.  Make sure it has dbowner on the site database.  Also, bear in mind that if you are using a mixed mode account (i.e. named and not a Windows account), you will actually need to remove the account from the database and re-add it after a restore.  A named account in a database restored to a different server won't resolve correctly.  So, like this:

use [database]

DROP USER sqllogin

CREATE USER sqllogin FOR LOGIN sqllogin

exec sp_addrolemember 'db_owner', 'sqllogin'


 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Moving from own system to Microsoft AzureMoving from own system to Microsoft Azure


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