infolink

Friday, September 16, 2011

Error in DotNetNuke after Upgrade to 5.6.3 The file '/Admin/Users/Profile.ascx'


Recently I upgraded a DotNetNuke Project to 5.6.3. After the upgrade everything seemed fine. When I went into Visual Studio 2008 SP1 and opened the website and tried to compile I got a few errors. The main error that plagued me was: Error 3 The file '/Admin/Users/Profile.ascx' does not exist. \admin\Users\ViewProfile.ascx 2 .

I noticed the upgrade basically cleared out the /admin/users folder, except left the ViewProfile control. This seems to reference a control with the tag name “profile”.

To get around this error, simply delete the ViewProfile.aspx and it's code behind. Recompile and you should be fine.

How to solve Micrososft SQL Server 2008 R2 Error: 1813

Recently I had a machine go down. I was able to get into recovery mode and transfer off most of the files. When I rebuilt the machine and reinstalled SQL server, I tried to attached my old database from the backup I took.

When I went to attach my log file I got the following error:

Attach database filed for Server 'SERVERNAME\INSTANCE'. (Microsoft.SqlServer.Smo)

Additional Information:
An excepetion occured while excuting a Trasact-SQL statement or batch.
(Microsoft.SQLServer.ConnectionInfo)

Could not open new database 'YOURDATABASENAME'. CREATE DATABASE is aborted.
File activation failure. The physical file name 'LOG FILE LOCATION' may be incorrect. The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environmental failure. (Microsoft SQL Server, Error: 1813)


Unfortunatly, the SQL log file was currupt and I didn't have a copy due to the server going down. So now what!?!?


The Solution:

Create a new database with the same exact name.

CREATE DATABASE YOURDATABASENAME
GO

Now stop Micrososft SQL Server.
Replace the MDF file with the old MDF file.
Start Micrososft SQL Server.

If everything went well the database should be in "Suspect" mode, which you check by running this:

SELECT DATABASEPROPERTYEX ('YOURDATABASENAME', 'STATUS') AS 'Status';
GO

Your database should now be in 'SUSPECT' mode.

Let's put her in emergency mode:

ALTER DATABASE YOURDATABASENAME SET EMERGENCY;
GO

Then single user mode:

ALTER DATABASE YOURDATABASENAME SET SINGLE_USER;
GO

And Finally:
DBCC CHECKDB (YOURDATABASENAME, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS;
GO



Buy Me a Beer

Tuesday, September 13, 2011

DotNetNuke Upgrade Paths

I was poking around to find the proper upgrade path for upgrading DotNetNuke. I found this post by Will Strohl:

http://www.willstrohl.com/Blog/EntryId/102/Suggested-DotNetNuke-Site-Upgrade-Path-s

Which shows the following chart:

From VersionTo Version
02.00.04External Link02.01.02External Link
02.01.02External Link03.01.01External Link
03.01.01External Link03.02.02External Link
03.02.02External Link04.03.07External Link *
04.03.07External Link04.04.01External Link
04.04.01External Link04.06.02External Link
04.06.02External Link04.09.05External Link
04.09.05External Link05.04.04External Link **
05.04.04External Link05.05.00External Link
05.05.00External Link05.06.02External Link



Upgrade URL to fire the install:
YOURDOMAIN/install/install.aspx?mode=Install

I was currently working with version 4.9.1 for our client and going from one version to another just seemd like such a pain. Especially since the scripts sometimes fail for no reason and when run again, run fine. So I went from 4.09.01 to 5.06.02 and the script ran but the HTML_Community core module kept failing durring the upgrade, it was the only failure in my logs.

I found the error eventually, and it turns out one of our vendors had added a Full Text Index on the HTML_Text table. Once I removed the FULL TEXT from the table and reran the upgrade, direct from 4.9.1 to 5.6.3, it ran without any errors at all.

While I believe the upgrade path is good advice if you have issues, I would recommend doing a direct upgrade to the latest first, if you get errors then follow the upgrade path, elsewise, save yourself some time and try the latest stable version upgrade first.

Saturday, August 13, 2011

Navigation to the webpage was cancelled and cannot view CHM help file in Windows 7

I was having a hard time viewing some documentation sent to me on an installation deployment. I was sent a .chm file. When I tried to open the chm help file I would see the index, but on the right side I would see “Navigation to the webpage was canceled". I then decided to check the properties of the file and noticed this button called unblock file. Once I clicked this I then hit OK and opened the chm file again and I could now view the file.

So to view html compiled help files in Windows 7 you may have go into the properties and unblock the file.

Sunday, August 7, 2011

TF255324: The specified database already exists. While installing Team Foundation Server 2010

[ Reporting ] TF255272: The database for SQL Server Analysis Services could not be verified. The problem is: TF255324: The specified database already exists. The database name is Tfs_Analysis.
That was the error I kept from reporting services during the Team Foundation Server 2010 readiness check.

You must go into SQL Management studio and connect to SQL Analysis Services Server and delete this database to proceed. This can be done by the following:

Open the SQL Services Management Studio. When the connection prompt comes up simply select SQL Analysis Services. Select your server and log in.Expand mthe cube and right click the Database and delete.

Please Donate To Bitcoin Address: [[address]]

Donation of [[value]] BTC Received. Thank You.
[[error]]

Friday, August 5, 2011

Installing Microsoft Team Foundation Server 2010

OK, for the last few days I have been installing Microsoft Team Foundation Server 2010.

I will try to sum up what I have seen thus far and what to do.

First thing is make sure you have all current Microsoft Updates: http://update.microsoft.com .

On my server I have Microsoft® SQL Server® 2008 R2 SP2 installed. You can use SQL server express if you would like, make sure to get the advanced services though, as reporting services and a many other tools:

Microsoft® SQL Server® 2008 Express with Advanced Services:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1842

Make sure to run Microsoft Update to apply any updates needed after the install of Microsoft® SQL Server® 2008
Here is a direct link for Microsoft SQL Server 2008 Service Pack 2:
http://www.microsoft.com/download/en/details.aspx?id=12548

Also you will need Microsoft SharePoint Services. You can also use Microsoft SharePoint Server, but for this I will use Windows SharePoint Services 3.0 with Service Pack 2 which can be downloaded from here:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20614

Now do all your updates again.
Since this machine is 64-bit, I got an error right off the bat, telling me that I could not install Microsoft SharePoint Services x64.
It is summed up here, this tells you how to disable IIS 32-bit emulation mode:
http://jamesecampbell.blogspot.com/2011/08/sharepoint-services-30-install-error.html
Now, make sure SQL Reporting service is configured and accessible.

This can be done using the Reporting Services Configuration Tool:
http://msdn.microsoft.com/en-us/library/ms156305.aspx

OK, now you are ready to install Microsoft Team Foundation Server 2010.






Monday, August 1, 2011

Sharepoint Services 3.0 Install error Windows 2008n R2 SP1 x64

Today I was trying to install Sharepoint Services 3.0 with SP2 on a Windows 2008 R2 X64 machine. Setup would not run as I got the error:

Setup is unable to proceed due to the following error(s):
Internet Information Services is running in 32-bit emulation mode.
Correct the issue(s) listed above to re-run setup.

So basically it looks like by default Internet Information Services is installed in 32 bit-emulation mode.

To disable this you simply need to do the following:

open a command line
copy and paste the following-
CScript "%SystemDrive%\InetPub\AdminScripts\adsutil.vbs" set w3svc/AppPools/Enable32bitAppOnWin64 0

Then type IISreset

Then try to re-run setup for Sharepoint Service 3.0 with SP2

If you need the link for Sharepoint Services 3.0 with SP2 X64:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5719

Amazon1