If you are trying to install .Net Core on your server and you get the error:
.Net Core 1.0.1 VS 2015 Tooling Preview 2 - Installation Error 0x80070003 - The system cannot find the path specified.
That only means the install packages are not complete so we have to completed the installation; to do it follow the next steps:
- Open the command line
- Run the .Net Core installation file with the layout parameter from the command like
- You should get the confirmation message that .Net Core was successfully installed
This is a blog where you are going to find tips or solution that are going to be helpful in the technology environment.
Wednesday, June 7, 2017
Thursday, April 28, 2016
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
If you get the error:
Looks like you upgraded recently your project to a newer version.
To solve this problem, follow the next steps:
* In Visual Studio, select your web project
* In the properties section set the Managed Pipeline Mode to Classic
* Compile and re-run the web application
HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
Looks like you upgraded recently your project to a newer version.
To solve this problem, follow the next steps:
* In Visual Studio, select your web project
* In the properties section set the Managed Pipeline Mode to Classic
* Compile and re-run the web application
Tuesday, February 23, 2016
MVC error on IIS 7 and 7.5 The Web server is configured to not list the contents of this directory.
If you get the error:The Web server is configured to not list the contents of this directory.
It is because the MVC URLs end without .aspx, these will not be picked up by IIS and run through the intergrated pipeline and therefore you will end up with 404 not found errors.
Another possible cause is you are using a .Net 4.5 application on a server where it was installed after IIS.
To solve this problem consider how much traffic you will have on your site, if you are not going to have a lot of traffic use the attribute runAllManagedModulesForAllRequest with true value, but keep in mind all your registered HTTP modules run on every request, not just managed requests (e.g. .aspx). This means modules will run on ever .jpg .gif .css .html .pdf etc.
But if you are going to have a lot of traffic it is better to add the routing module:
Another solution is to install a patch from Microsoft that enables certain IIS 7.0 or IIS 7.5 handlers to handle requests whose URLs do not end with a period.
This is the link to download this patch:
https://support.microsoft.com/en-us/kb/980368
It is because the MVC URLs end without .aspx, these will not be picked up by IIS and run through the intergrated pipeline and therefore you will end up with 404 not found errors.
Another possible cause is you are using a .Net 4.5 application on a server where it was installed after IIS.
To solve this problem consider how much traffic you will have on your site, if you are not going to have a lot of traffic use the attribute runAllManagedModulesForAllRequest with true value, but keep in mind all your registered HTTP modules run on every request, not just managed requests (e.g. .aspx). This means modules will run on ever .jpg .gif .css .html .pdf etc.
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
But if you are going to have a lot of traffic it is better to add the routing module:
<system.webServer>
<modules>
<remove name="UrlRoutingModule-4.0" />
<add name="UrlRoutingModule-4.0"
type="System.Web.Routing.UrlRoutingModule"
preCondition="" />
</modules>
</system.webServer>
Another solution is to install a patch from Microsoft that enables certain IIS 7.0 or IIS 7.5 handlers to handle requests whose URLs do not end with a period.
This is the link to download this patch:
https://support.microsoft.com/en-us/kb/980368
Wednesday, January 20, 2016
SSIS Error: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
If you get the error:
Error: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
If the problem is in your development studio, you can fix it by running the package in 32 bit mode on your project:
Error: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
If the problem is in your development studio, you can fix it by running the package in 32 bit mode on your project:
- Right-click your solution
- Click 'Properties'
- Select 'Debugging' node
- Set 'Run64BitRuntime' property to False
- Save and re-run your solution
- Click Apply
- Re-run your package
If the problem is in your SQL server put your package in a job and change the run time to 32bit:
- Go to SQL Serve Agent option
- Right click on Jobs and select
- Go to steps and click on New
- Fill out the options with your package information
- Click on configuration
- Click on Advance
- Check on 32 bit
- Click on OK
- Complete your job and run it
Thursday, December 31, 2015
How to convert string to variable name in Javascript
If you need to create a variable dynamically on the server side and retrieve the value on the client side, use the next example to use the value assigned:
You can even assign a function to the dynamic string variable:
//
Declare the variable name
var myStringName = "echoHello";
//
Assign a value to the dynamic string variable
window[myStringName]
= "Hello from dynamic string
variable!";
//
Show value
alert(window[myStringName]);
//
Or call the variable name
alert(echoHello);
You can even assign a function to the dynamic string variable:
//
Declare the variable name
var myStringName = "alertStringVariable";
//
Assign a function to the dynamic variable
window[myStringName]
= function
() {
alert("Hello
from dynamic function variable...");
}
//
Execute the function assigned of the variable
alertStringVariable();Thursday, November 19, 2015
How to stop execution of SSIS Package from SSMS
If your package is running and you want to stop it from the SQL Management Studio follow this steps:
1.- Go to the Integration Services Catalogs and select the SSISDB catalog
2.- Go to the SSISDB catalog Right Click and select the “Active Executions”
3.- You will see the currently running packages, select the desired package then click STOP
How to map network drives programmatically in C#
Follow the next example to map a network drive programmatically:
//
Map Network drive
System.Diagnostics.Process process = new System.Diagnostics.Process();
System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo();
//
Notes:
// Use /C To carry out the command specified
by string and then terminates
// You can omit the passord or username and
password
// Use /PERSISTENT:YES to keep the mapping
when the machine is restarted
psi.FileName = "cmd.exe";
psi.Arguments = @"/C
net use X: \\MyServer\Folder01
/USER:MyDomain\MyUsername MyPassword /PERSISTENT:YES";
psi.WindowStyle = System.Diagnostics.ProcessWindowStyle.Normal;
process.StartInfo
= psi;
process.Start();
Subscribe to:
Posts (Atom)


