SSIS Error - The value cannot be converted because of a potential loss of data

Error

[OLE DB Source [167]] Error: There was an error with OLE DB Source.Outputs[OLE DB Source Output].Columns[MyColumn] on OLE DB Source.Outputs[OLE DB Source Output]. The column status returned was: "The value could not be converted because of a potential loss of data.".

Solution

Go into the source component then right clicking on it and choose "Show Advanced editor..."

From the Advance Editor select Input and Output Properties

Expand the OLE DB Source Output
Then expand the Output Columns
Select the column generating the error

O the properties section, scroll to the Length Data Type Property and increase the value to  something like 255.

MVC Core error - HTTP Error 502.5 - Process Failure

If you are deploying your project to Internet Information Services and you get the error below, there are several possible reasons according with microsoft.

Possible reasons:

• If you published a self-contained application, confirm that you didn’t set a platform in buildOptions of project.json that conflicts with the publishing RID. For example, do not specify a platform of x86 and publish with an RID of win81-x64 (dotnet publish -c Release -r win81-x64). The project will publish without warning or error but fail with the above logged exceptions on the server.
• Check the processPath attribute on the element in web.config to confirm that it is dotnet for a portable application or .\my_application.exe for a self-contained application. For a portable application, dotnet.exe might not be accessible via the PATH settings. Confirm that C:\Program Files\dotnet\ exists in the System PATH settings.
• For a portable application, dotnet.exe might not be accessible for the user identity of the Application Pool. Confirm that the AppPool user identity has access to the C:\Program Files\dotnet directory. Confirm that you have correctly referenced the IIS Integration middleware by calling the .UseIISIntegration() method of the application’s WebHostBuilder().
• If you are using the .UseUrls() extension method when self-hosting with Kestrel, confirm that it is positioned before the .UseIISIntegration() extension method on WebHostBuilder(). .UseIISIntegration() must set the Url for the reverse-proxy when running Kestrel behind IIS and not have its value overridden by .UseUrls().

I got this error, but in my case the problem was I didn't declared the environment variable ASPNETCORE_ENVIRONMENT, so the application wasn't able to get the appsettings..json file; after I added the variable I restarted the server and my site worked just fine.

ASP MVC Error Unable to connect to web server IIS Express

If you get the next error when trying to run your app from visual studio:

You can try different things to fix the problem

- Right click on your project, then select properties, click on the Debug section, assign a new port in the App URL direction

- In explorer go to the path \.vs\config and delete the applicationhost.config, then rebuild your project 

- Open the task manager and stop the IIS Express if is running so you can get a fresh instance

.Net Core Installation Error 0x80070003 - The system cannot find the path specified

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

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

If you get the error:

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

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.

  <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

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:

1. Right-click your solution
2. Click 'Properties'
3. Select 'Debugging' node
4. Set 'Run64BitRuntime' property to False
5. Save and re-run your solution
6. Click Apply
7. 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:

1. Go to SQL Serve Agent option
2. Right click on Jobs and select 
3. Go to steps and click on New
4. Fill out the options with your package information
5. Click on configuration
6. Click on Advance
7. Check on 32 bit
8. Click on OK
9. Complete your job and run it