Web Service asmx Request format is unrecognized for URL unexpectedly ending in ‘/anything’

This short blog shows you how to resolve the error in Web Service asmx “Request format is unrecognized for URL unexpectedly ending in ‘xxxxxx’ “.

I have a .NET Web Service utilizing a class name ReceivedATA. Somehow when I am browsing it then it show the error below.

Request format is unrecognized for URL unexpectedly ending in ‘/ReceivedATA’

I have no clue of what the message is about totally. I found the link in Internet (the link is the reference). This link is saying if I disable the friendly error message than I am able to see the meaningful error.

So I open IE, choose Internet options, choose again the Advance tab then unclicked the Show friendly HTTP error messages.

Once I have done that then I see the error message below that I know how to resolve the problem. At least I know which file and which line is the issue on.

System.NullReferenceException: Object reference not set to an instance of an object.

at WebServiceCustoms.WebServiceATA.ReceivedATA() in C:\dev1\WebServiceCustoms\WebServiceCustoms\WebServiceATA.asmx.cs:line 57

Reference:

https://social.msdn.microsoft.com/Forums/en-US/dacbe7e4-b993-4325-b61c-e1fef533d810/webservice-error-request-format-is-unrecognized-for-url-unexpectedly?forum=asmxandxml

https://support.isqsolutions.com/article.aspx?id=10161

Advertisements

SSIS If the 64-bit driver is not installed, run the package in 32-bit mode

This short blog shows you how to resolve the Oracle error “If the 64-bit driver is not installed, run the package in 32-bit mode” in SSIS

When you are running SSIS with Oracle Data Access Components, and you schedule to run your jobs then you might get the error below.

Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 12.0.5000.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:58:15 PM Error: 2017-07-10 15:58:16.15 Code: 0xC0209303 Source: ssisDashboard_ODD_1 Connection manager “EXPDEV.EXPRESS” Description: The requested OLE DB provider OraOLEDB.Oracle.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: “Microsoft OLE DB Service Components” Hresult: 0x80040154 Description: “Class not registered”. End Error Error: 2017-07-10 15:58:16.15 Code: 0xC020801C Source: Data Flow Task EXPDEV EXPRESS [49] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager “EXPDEV.EXPRESS” failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2017-07-10 15:58:16.15 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: EXPDEV EXPRESS failed validation and returned error code 0xC020801C. End Error Error: 2017-07-10 15:58:16.15 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2017-07-10 15:58:16.15 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:58:15 PM Finished: 3:58:16 PM Elapsed: 0.235 seconds. The package execution failed. The step failed.

Again, in a big chuck of wording the useful words are only 7 of it.

Open your SSIS job in SQL Job Agent. Get to the SSIS Step. Click on the Execution Options then check the Use 32 bit runtime checkbox.

Windows 10 phone Waze searching network

This short blog shows one of the reasons Waze is searching network in Windows 10 mobile.

Out of sudden Waze quitted automatically each time when I pressed the Go button after the destination was found.

So I uninstalled and reinstalled the Waze. After installed Waze and I launched it.

When came to the login part then I pressed Skip.

Since then onward Waze is giving me Searching network error.

I fixed it by creating a Waze account and login. The Waze magically working fine after the login.

This is the price you need to pay for free apps. Are they really free?

Visual Studio 2017 installation failed

This is a quick blog is just tells you one of the reason my Visual Studio 2017 keep failing.

I still having a machine running Windows 10 build 1507. In this version I could never installed Visual Studio 2017 successfully. It keep failing Visual Studio installation with funny logs.

I upgrade from Windows 10 build 1507 to 1703 Creator Update. It succeeded the installation with only one time.

Windows 10 Prevent Windows from Automatically Updating Specific Drivers

This short blog shows you how to prevent Windows 10 auto update your driver and crash your machine.

For me, my AMD graphic driver always crash after auto update.

1. Click on the Start button on your Windows 10 then type Device Manager.

2. Device Manager window will open once you click on the Device Manager.

3. I chose Display adapters.

4. Right click on AMD Radeon 6600M and 6700M Series. Choose Properties.

5. Click on the Details tab. Choose Hardware Ids from the drop dropdown.

Copy all the Value such as below.

PCI\VEN_1002&DEV_6741&SUBSYS_06001025&REV_00

PCI\VEN_1002&DEV_6741&SUBSYS_06001025

PCI\VEN_1002&DEV_6741&CC_030000

PCI\VEN_1002&DEV_6741&CC_0300

6. Click on Start button again and type gpedit Click on Edit group policy.

9. Choose Administrative Templates in Computer Configuration.

10. Select System. Select again Device Installation then in Device Installation Restriction
Prevent double click the installation of devices that match any of these device IDs.

11. Click the Enable radio button then the Show… button will be enable.

12. Click on the Show… button and enter the values that you have copy.

You will then prevent the driver from installing until you remove the values.

Reference:

https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/

Power BI license to access Power BI Dashboard

This short article is showing you what are the license you really need when accessing to a Dashboard that is shared by Power BI.

Many vendors will be telling you anyone can access to Power BI shared dashboard, or you only need Office 265 E3 license, or even tell that you just need an Outlook email account, and others fabulous stories.

All these fantastic stories are untrue. Thanks to one of the vendor lending me one Office 365 E5 user account and another Office 365 E3 user account.

For the below testing I first use E5 user to share the Power BI dashboard to E3 user and vice versa.

Publish using Office E5 try to access using Office E3

Publish a report using E5 user.

Publishing Done

Access to the Dashboard using E5 user.

Share the Dashboard with E3 user.

E3 user will receive an email.

E3 user cannot access unless it is with Power BI Pro user.

The shared will also appear in the E3 using notification area.

Publish using E3 try to access using E5

E3 can publish the report to Power BI cloud.

Sharing with E5. Again Power BI Pro is needed.

The conclusion is, you need Power BI Pro or an Office 365 E5 license to access to Power BI shared dashboard.

SSIS Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80040154 Class not registered

This short blog shows you how to resolve another not so meaningful error message that you will encounter if your SSIS package is connecting to Excel.

When you look at the error message below then what action should you take?

Executed as user: xxx.COM.MY\xxxxx C:\Windows\system32>c:\temp\qc\input\ConAppExcelDelimiter.exe 1 Unhandled Exception: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at ConAppExcelDelimiter.ReadExcelFile.ReadExcel(String strFileName, Int32 RowCount, Int32 ColCount, String strDelimiter, Int32 intSheet) at ConAppExcelDelimiter.Program.Main(String[] args). Process Exit Code 255. The step failed.

I resolved this problem by installing the 32 bit Excel the correct term should be Office 2013 Standard into the Windows Server. You only need to install it, no need to do any activation. So actually no additional Office 2013 license is required.