We have been increased 2000 followers in last 2 weeks, it is excellent system which can increase your followers list in your twitter account.
Click Here
This blog is about developers who are working on MS Technologies and mobile development. You can find very interesting stuff related to MS Technologies like ASP.NET, C#, VB.NET, SharePoint 2003, SharePoint 2007, MS SQL SERVER 2000 , MS SQL SERVER 2005, MS SQL SERVER 2008 and about latest technologies. Also people can also post stuffs related MS Dynamics CRM 3.0, MS Dynamics CRM 4.0 , MS Dynamics GP, Ms Dynamics Soloman.
Sunday, November 29, 2009
Wednesday, October 28, 2009
The server rejected the sender address. The server response was: 530 5.7.0 Must issue a STARTTLS command first
Cause: When you are going to send mail in asp.net 1.1 by using google smtp server.then generally following error come.
Error:"The server rejected the sender address. The server response was: 530
5.7.0 Must issue a STARTTLS command first. f42sm2050000rvb.9"
Solution: Basically problem is SSL and Port. you need to set smtpusessl true and smtpserverport is 465.
C# Code:
MailMessage mail = new MailMessage();
mail.From = "fromjai@gmail.com"; // put the from address here
mail.To = "tojai@domain.com"; // put to address here
mail.Subject = "Test"; // put subject here
mail.Body = "Testing 12345 "; // put body of email here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate", "1"); //basic authentication
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusing", "2"); //port to launch send
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusername", "reporting@domain.com"); //set your username here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendpassword", "yourpassword"); //set your password here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserverport", "465"); //set your port here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserver", "smtp.gmail.com"); //set your password here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpusessl", true); //set SSL option to true
// send the mail
SmtpMail.Send(mail);
hope this help.
Error:"The server rejected the sender address. The server response was: 530
5.7.0 Must issue a STARTTLS command first. f42sm2050000rvb.9"
Solution: Basically problem is SSL and Port. you need to set smtpusessl true and smtpserverport is 465.
C# Code:
MailMessage mail = new MailMessage();
mail.From = "fromjai@gmail.com"; // put the from address here
mail.To = "tojai@domain.com"; // put to address here
mail.Subject = "Test"; // put subject here
mail.Body = "Testing 12345 "; // put body of email here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate", "1"); //basic authentication
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusing", "2"); //port to launch send
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendusername", "reporting@domain.com"); //set your username here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/sendpassword", "yourpassword"); //set your password here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserverport", "465"); //set your port here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpserver", "smtp.gmail.com"); //set your password here
mail.Fields.Add("http://schemas.microsoft.com/cdo/configuration/smtpusessl", true); //set SSL option to true
// send the mail
SmtpMail.Send(mail);
hope this help.
Labels:
asp.net 1.1,
Mail
Sunday, September 20, 2009
: Could not load type 'System.Web.UI.ScriptReferenceBase' from assembly 'System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3
Installed Microsoft Framework 3.5 SP1.
Labels:
visual studio 2008
Thursday, September 17, 2009
System.UnauthorizedAccessException: Access to the path 'C:\inetpub\wwwroot\...' is denied
This exception is a very common exception. It usually occurs when we move our application to IIS server.
This exception occurs because IIS uses ASP .Net (IIS_IUser in Vista) user account and ASP .Net is not authorized to access that location.
To give a quick fix to this, follow these steps:-
1-Give read/write rights to ASP.NET user to C:\Inetpub\yourfolder\ folder:-
1- Right Click on Folder and Select Properties
2- Go to Security Tab
3- Click Add, then click Location.
4- Select your pc name, usually first item.
5- Press Ok, then press advance and then Find Now.
6- Select ASP.NET user if not exist then select Authenticated Users.
7- Press Ok. And Select Read/Write/Modify/List Folder Contents
2- Go to IIS->WebSites->DefaultWebSite->YourWebSiteName->Properties, and at Virtual Directory Tab check 'Read' and 'Write' button.
This exception occurs because IIS uses ASP .Net (IIS_IUser in Vista) user account and ASP .Net is not authorized to access that location.
To give a quick fix to this, follow these steps:-
1-Give read/write rights to ASP.NET user to C:\Inetpub\yourfolder\ folder:-
1- Right Click on Folder and Select Properties
2- Go to Security Tab
3- Click Add, then click Location.
4- Select your pc name, usually first item.
5- Press Ok, then press advance and then Find Now.
6- Select ASP.NET user if not exist then select Authenticated Users.
7- Press Ok. And Select Read/Write/Modify/List Folder Contents
2- Go to IIS->WebSites->DefaultWebSite->YourWebSiteName->Properties, and at Virtual Directory Tab check 'Read' and 'Write' button.
Wednesday, September 16, 2009
Operation must use an updateable query.
Hi one my friend is getting this error "Operation must use an updateable query"
Solution:
Error Message:
Operation must use an updateable query. /file.asp 12
Cause:
The most common reason this error is generated is the database or directory containing the database you are trying to access does not have the correct permissions.
Resolution:
Either move the database to the "access_db" directory or add read/write permissions to the directory where the database resides.
Solution:
Error Message:
Operation must use an updateable query. /file.asp 12
Cause:
The most common reason this error is generated is the database or directory containing the database you are trying to access does not have the correct permissions.
Resolution:
Either move the database to the "access_db" directory or add read/write permissions to the directory where the database resides.
Labels:
access database,
godaddy
Thursday, September 3, 2009
Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.
Error: Error while trying to run project: Unable to start debugging on the web server. The project is not configured to be debugged.
Cause: Either debug is not enabled in your web.config (OR) For some reasons IIS is not considering your web application as a virtual directory. Instead it is considering it to be a normal folder.
Solution 1:
Step 1: Open the web.config
Step 2: If debug is set to "false" change it to "True".
For example: In web.config I have a line like this I would change it to
If at all this doesn't work. Try out the next solution.
Solution 2:
1.From the Start menu, choose Programs, then Administrative Tools, and click Internet Information Services.
2.In the Internet Information Services dialog box, click the tree control for your machine, open the Web Sites folder, and find your web site.
3.Right-click Web Site and choose Properties.
4.In the Web Site Properties window, select the Directory tab.
5.Under Application Settings, look for the Remove or Create button. If the button says Remove, your website is already configured as an application. If the button says Create, click the button to configure your website as an application.
6.Click OK.
If it also doesn't work, try the next solution.
Solution 3:
If you are running Visual Studio 2003 (or ASP.NET v1.1) you should setup IIS to use ASP.NET v1.1 and not ASP.NET v2.0
May be you have installed .NET framework 1.1 as well as 2.0 in your box and trying to run an application via VS.NET 2003. If so, then do the following:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Choose the tab ASP.NET
Step 5: The first dropdown would read "ASP.NET Version", choose 1.1.4322
Solution 4 :
1. go to the C:\WINNT\Microsoft.NET\Framework\
2. and run aspnet_regiis.exe /i
That's it. Hope this helps.
Cause: Either debug is not enabled in your web.config (OR) For some reasons IIS is not considering your web application as a virtual directory. Instead it is considering it to be a normal folder.
Solution 1:
Step 1: Open the web.config
Step 2: If debug is set to "false" change it to "True".
For example: In web.config I have a line like this
If at all this doesn't work. Try out the next solution.
Solution 2:
1.From the Start menu, choose Programs, then Administrative Tools, and click Internet Information Services.
2.In the Internet Information Services dialog box, click the tree control for your machine, open the Web Sites folder, and find your web site.
3.Right-click Web Site and choose Properties.
4.In the Web Site Properties window, select the Directory tab.
5.Under Application Settings, look for the Remove or Create button. If the button says Remove, your website is already configured as an application. If the button says Create, click the button to configure your website as an application.
6.Click OK.
If it also doesn't work, try the next solution.
Solution 3:
If you are running Visual Studio 2003 (or ASP.NET v1.1) you should setup IIS to use ASP.NET v1.1 and not ASP.NET v2.0
May be you have installed .NET framework 1.1 as well as 2.0 in your box and trying to run an application via VS.NET 2003. If so, then do the following:
Step 1: Start >> Run >> inetmgr
Step 2: Navigate to the virtual directory of the project which is throwing this error.
Step 3: Right click on the virtual directory and choose "Properties"
Step 4: Choose the tab ASP.NET
Step 5: The first dropdown would read "ASP.NET Version", choose 1.1.4322
Solution 4 :
1. go to the C:\WINNT\Microsoft.NET\Framework\
2. and run aspnet_regiis.exe /i
That's it. Hope this helps.
Labels:
.Net framework,
C#,
visual studio 2008
Error message when you connect to an instance of SQL Server: "Cannot open user default database"
Solution : 1
1- Go to database server -> security->login->username
2- Go to user property page and assign respective database or go to user role tab and give sysadmin permission to the user.
Solution-2
refer - http://support.microsoft.com/?id=307864
1- Go to database server -> security->login->username
2- Go to user property page and assign respective database or go to user role tab and give sysadmin permission to the user.
Solution-2
refer - http://support.microsoft.com/?id=307864
Labels:
ms sql server 2005
Thursday, July 9, 2009
Can Google Chrome OS ceates problem for Microsoft OS: What do you think ?
NEW YORK (Fortune) -- It's highly unlikely that the operating system Google announced yesterday -- dubbed Google Chrome OS -- will rocket to the heights of its chief competitor, Microsoft, right away. But it doesn't really matter. In a world obsessed with all things Google, the new OS will certainly get its fair share of attention, and the frontal assault on Microsoft that it represents will serve at least as a great distraction to the tech behemoth.
We only know a few details about Google's plans for the operating system, which won't actually launch until the fall of 2010. It will target netbooks initially and then expand to the larger PC market. It will combine the Google Chrome browser with a Linux kernel. Though there's some overlap with Android, the company's operating system for mobile devices, this system is intended for computers. And it will be fast, accessible, efficient, and -- though Google (GOOG, Fortune 500) hasn't said as much -- it's likely the operating system will be free.
Google's announcement is riddled with subtle jabs at its Seattle rival, even going so far as calling the Chrome OS necessary because "the operating systems that browsers run on were designed in an era where there was no web."
But there's a lot to suggest Google won't be able to pull this off. The company's only breakthrough success has come with the AdWords and AdSense products related to its core business -- search. While Google's launched plenty of products over the years, it's sometimes hard to tell immediately whether they're designed to dominate a field or entertain technologists.
And many of those products have not risen to prominence. Google Apps just came out of beta this week, but it's hardly affected Microsoft Office's dominance in productivity. Google product search -- you may remember it as Froogle -- was a flop. Google Checkout hasn't overtaken PayPal, and Knol was far from a Wikipedia-killer. Does anyone even remember Orkut, an early contender for the market Facebook has captured? And the list goes on.
Still, Google's announcement should worry Microsoft (MSFT, Fortune 500). It's the biggest threat yet to the tech giant's crown jewels, and it's more evidence of the growing agitation in the tech industry: Google joins a number of other large tech companies that have quietly begun work on their own operating systems. (Intel (INTC, Fortune 500), for example, recently announced Moblin, a Linux-based operating system for netbooks.)
Microsoft has yet to publicly react to Google's announcement of the Chrome OS, which will debut at the same time as the much-anticipated new version of Microsoft's own operating system, Microsoft Windows 7, this fall. Early reviews of Windows 7 have been promising, but Microsoft faces a significant hurdle with the poor reception of its last offering, Vista. Now, it will also have to launch in the shadow of a new competitor that -- while it doesn't even exist yet -- has already begun to steal the show.
We only know a few details about Google's plans for the operating system, which won't actually launch until the fall of 2010. It will target netbooks initially and then expand to the larger PC market. It will combine the Google Chrome browser with a Linux kernel. Though there's some overlap with Android, the company's operating system for mobile devices, this system is intended for computers. And it will be fast, accessible, efficient, and -- though Google (GOOG, Fortune 500) hasn't said as much -- it's likely the operating system will be free.
Google's announcement is riddled with subtle jabs at its Seattle rival, even going so far as calling the Chrome OS necessary because "the operating systems that browsers run on were designed in an era where there was no web."
But there's a lot to suggest Google won't be able to pull this off. The company's only breakthrough success has come with the AdWords and AdSense products related to its core business -- search. While Google's launched plenty of products over the years, it's sometimes hard to tell immediately whether they're designed to dominate a field or entertain technologists.
And many of those products have not risen to prominence. Google Apps just came out of beta this week, but it's hardly affected Microsoft Office's dominance in productivity. Google product search -- you may remember it as Froogle -- was a flop. Google Checkout hasn't overtaken PayPal, and Knol was far from a Wikipedia-killer. Does anyone even remember Orkut, an early contender for the market Facebook has captured? And the list goes on.
Still, Google's announcement should worry Microsoft (MSFT, Fortune 500). It's the biggest threat yet to the tech giant's crown jewels, and it's more evidence of the growing agitation in the tech industry: Google joins a number of other large tech companies that have quietly begun work on their own operating systems. (Intel (INTC, Fortune 500), for example, recently announced Moblin, a Linux-based operating system for netbooks.)
Microsoft has yet to publicly react to Google's announcement of the Chrome OS, which will debut at the same time as the much-anticipated new version of Microsoft's own operating system, Microsoft Windows 7, this fall. Early reviews of Windows 7 have been promising, but Microsoft faces a significant hurdle with the poor reception of its last offering, Vista. Now, it will also have to launch in the shadow of a new competitor that -- while it doesn't even exist yet -- has already begun to steal the show.
Labels:
Google Chrome,
Microsoft killer,
Operating System
Sunday, July 5, 2009
AJAX Control Toolkit: Active Tab Changed Event in Tab control is not working
By default, when we use the OnActiveTabChanged event in Tab control in AJAX control toolkit it will not call the server side event we need to set the AutoPostBack property to true.
Solution: AutoPostBack="true" in TabContainer Control.
Solution: AutoPostBack="true" in TabContainer Control.
Labels:
AjaxToolKit
Tuesday, June 30, 2009
Problem to open .CHM file
Open Windows Explorer, right-click on the CHM file, and select Properties from the popup menu. Click on the Unblock button immediately below the Advanced button on the General page. Click Apply to show the content.
Hope this helps.
Hope this helps.
Labels:
HTML files
Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution : visit http://www.interviewsworld.com
Exception Details: System.Data.SqlClient.SqlException: Login failed for user [user name]. Reason: Server is in single user mode. Only one administrator can connect at this time.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution : visit http://www.interviewsworld.com
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution: viewview Solution
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Solution: viewview Solution
Labels:
.net,
.Net framework,
asp.net 3.5,
C#,
visual studio 2008
Cannot create/shadow copy [Project File Name] when that file already exists.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Cannot create/shadow copy 'Test.UI' when that file already exists.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Test.UI' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Solution : visit View Solution
Exception Details: System.IO.FileLoadException: Cannot create/shadow copy 'Test.UI' when that file already exists.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Test.UI' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Solution : visit View Solution
Labels:
.net,
asp.net,
C#,
visual studio 2008
Monday, June 15, 2009
Changing the default browser used in VS 2008 and Visual Web Developer
I have seen a few people ask if it is possible to change what browser is launched and used when running web applications in VS 2008 and Visual Web Developer (for example:Chrome, Firefox instead of IE). It is an easy way to configure this.
Below is steps:
1) Right click on a .aspx page in your solution explorer
2) Select the "browse with" context menu option
3) In the dialog you can select or add a browser. If you want Firefox in the list, click "add" and point to the firefox.exe filename
4) Click the "Set as Default" button to make this the default browser when you run any page on the site.
Note that there is also an optional drop-down at the bottom of the dialog that lets you select the default browser window size when loading. You can choose 800x600 or 1024x768 if you want to visualize what the site will look like for people using those screen resolutions. This works for both IE and FireFox (and probably other browsers too -- those just happened to be the two I checked).
Hope this helps,
www.interviewsworld.com
Below is steps:
1) Right click on a .aspx page in your solution explorer
2) Select the "browse with" context menu option
3) In the dialog you can select or add a browser. If you want Firefox in the list, click "add" and point to the firefox.exe filename
4) Click the "Set as Default" button to make this the default browser when you run any page on the site.
Note that there is also an optional drop-down at the bottom of the dialog that lets you select the default browser window size when loading. You can choose 800x600 or 1024x768 if you want to visualize what the site will look like for people using those screen resolutions. This works for both IE and FireFox (and probably other browsers too -- those just happened to be the two I checked).
Hope this helps,
www.interviewsworld.com
Labels:
.net 3.5,
visual studio 2008
Tuesday, May 26, 2009
.Net Error Message: .Net 3.0 & 3.5 installation errors
Error Message:
[11/21/07,08:52:42] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,08:55:36] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:10:30] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:10:36] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:12:06] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:12:11] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:25:28] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:25:32] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:38:12] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:38:17] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:43:32] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:56:03] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:56:08] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,10:15:10] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,10:38:23] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,10:38:28] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
Solution:
First - 1
Stop the World Wide Web service.
Open IIS and try to stop it from there, or goto My Computer. Right Click. Manage Services.
Then close service named World Wide Web Publishing.
Second- 2
1. Uninstall IIS service and related components.
2. Reinstall IIS server and asp.net etc.
3. Install .Net 3.5 .
[11/21/07,08:52:42] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,08:55:36] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:10:30] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:10:36] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:12:06] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:12:11] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:25:28] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:25:32] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:38:12] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:38:17] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,09:43:32] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:56:03] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,09:56:08] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
[11/21/07,10:15:10] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,10:38:23] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[11/21/07,10:38:28] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.
Solution:
First - 1
Stop the World Wide Web service.
Open IIS and try to stop it from there, or goto My Computer. Right Click. Manage Services.
Then close service named World Wide Web Publishing.
Second- 2
1. Uninstall IIS service and related components.
2. Reinstall IIS server and asp.net etc.
3. Install .Net 3.5 .
Labels:
.net 3.5
Error Message: Internet Explorer cannot open the internet site [the requested URL like www.interviewsworld.com]. Operation aborted
Visiting a Web page in Internet Explorer 5.5/6.0/7.0 will give this error. Internet Explorer cannot open the Internet site http://www.interviewsworld.com. Operation aborted.
This error will not occur in firefox, opera and Internet Explorer 8.0.
Cause:
This problem occur if a DIV element is a child container in a BODY element, and a SCRIPT block in the DIV element tries to modify the BODY element that is a parent container for the DIV element.
This error will not occur in firefox, opera and Internet Explorer 8.0.
Cause:
This problem occur if a DIV element is a child container in a BODY element, and a SCRIPT block in the DIV element tries to modify the BODY element that is a parent container for the DIV element.
Labels:
.Net framework
Dot Net Error : Internet Explorer cannot open the internet site [www.sample.com]. Operation aborted
Description: Visiting a Web page in Internet Explorer 5.5/6.0/7.0 will give this error. Internet Explorer cannot open the Internet site http://.com. Operation aborted. This error will not occur in firefox, opera and Internet Explorer 8.0.
Cause: This problem occur if a DIV element is a child container in a BODY element, and a SCRIPT block in the DIV element tries to modify the BODY element that is a parent container for the DIV element.
Save this page as a html file and run in internet explorer will generate same error.
This problem generally occurs while implementation Ajax, or using Modal Dialog box.
Solutions
Solution 1: Upgrade to Internet Explorer 8
Solution 2: Try to change the position of div tag.
Place script tag outside of div tag.
Solution 3: If you are getting error in below senario.
Try to move the position of script tag.
Cause: This problem occur if a DIV element is a child container in a BODY element, and a SCRIPT block in the DIV element tries to modify the BODY element that is a parent container for the DIV element.
Save this page as a html file and run in internet explorer will generate same error.
This problem generally occurs while implementation Ajax, or using Modal Dialog box.
Solutions
Solution 1: Upgrade to Internet Explorer 8
Solution 2: Try to change the position of div tag.
Place script tag outside of div tag.
Solution 3: If you are getting error in below senario.
Try to move the position of script tag.
Labels:
.Net Framework,
asp.net
Friday, May 22, 2009
Reading last line in text file
StreamReader streamReader = new StreamReader("HereWillBeYourTextFilePath");
ArrayList lines = new ArrayList();
string line;
while ((line = streamReader.ReadLine()) != null)
{
lines.Add(line);
}
streamReader.Close();
if (lines.Count > 0)
{
Response.Write(lines[lines.Count - 1].ToString());
}
ArrayList lines = new ArrayList();
string line;
while ((line = streamReader.ReadLine()) != null)
{
lines.Add(line);
}
streamReader.Close();
if (lines.Count > 0)
{
Response.Write(lines[lines.Count - 1].ToString());
}
Labels:
C#
Subscribe to:
Posts (Atom)