Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

GarryBrown — Wed, 13 Mar 2013 15:35:21 GMT

Thanks for the information. Also try Long Path Tool. It helped me with Error 1320 on Win 7. :)

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Jill_M [MSFT] — Fri, 07 Dec 2012 16:46:55 GMT

Andy, I'm asking around for you. I searched my email archives and didn't get any hits. I'll let you know what I hear.

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Andy — Thu, 06 Dec 2012 16:40:08 GMT

Eveer seen this?

I have imported some OMPM scans into the SQL Express database (1 database per scan) and on one of them, it reports that the import was successful and by using the SQL Management Studio I can see that it was going by the size of the DB but after connecting to the database which it seems to do OK when using OMPM.accdr there is no data. The SCan ID shows in the drop down but there are 0 records.

It also sometimes gives the following error message:

ODBC --CALL FAILED.

[Microsoft][ODBC SQL Server Driver]Query timeout expired (#0)

Can anyone please advise?

Thanks

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Andy — Fri, 16 Nov 2012 13:58:14 GMT

Thanks for your reply.

I have found that distributing down the scans even further has (so far) stopped this error. I did read that its due to some MS security updates around remote execution but I am not convinced that is the cause. I have a feeling this may be more related to the amount of data being held in memory or buffering over the network causing this.

So far so good anyway with splitting the scans down further to more machines hitting the server I am scanning each taking a smaller section.

I will let you all know if this completes OK like this. So far I have scanned over 10TB of data with good results and useful info.

I have read a little about the Telemetry Dashboard and it does sound a good tool but having not tested it, this is something I will look at using in the future as I'm up against some deadlines which are fast approaching.

Many thanks all :)

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Jill_M [MSFT] — Wed, 14 Nov 2012 20:05:05 GMT

Hi Andy, I've seen this error reported once before and never could track down the issue. I know you have a lot of effort invested in OMPM and I'm sorry it's not working flawlessly for you. Any chance you'd be interested in trying Telemetry Dashboard instead?

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Andy — Wed, 14 Nov 2012 13:31:12 GMT

Has anyone come accross the HRESULT = 0x80070008 error in the xml logs created whilst running a scan?

Need some advise on what this is and how to fix it.

Thanks

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Jill_M [MSFT] — Tue, 06 Sep 2011 20:43:00 GMT

Matthew, you can post your OMPM experiences on this blog or in the Office Compat forum here:

social.technet.microsoft.com/.../threads

What were the issues you hit with SQL and Server 2008 R2? I believe we tested on these versions for the recent update to OMPM in late July 2011.

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Matthew Gailer — Mon, 05 Sep 2011 22:19:52 GMT

I also found the above fix worked for another similar error ("Type of column ‘ErrorInfo’ in table ‘osError’ is too small to hold data") by expanding the ErrorInfo field in the table.

Now, if only I could rewind about 2 weeks to know this plus other things with OMPM I would have saved myself plenty of time. No.1 time saver would have been to always install SQL Server 2005 on 32-bit Windows Server 2003. Anything above that was a major issue - especially 64-bit. Any chance the OMPM team might be working on a product that import successfully with Server 2008 R2 and SQL Server 2008 R2?

re: Experience from the Field: Resolving the OMPM issue “Type of column ‘WarningInfo’ in table ‘osWarning’ is too small to hold data”

Matthew Gailer — Mon, 05 Sep 2011 05:08:25 GMT

I also found a similar issue with the column "ErrorInfo" in the osError table. Applied the same fix as per above by increasing the nvarchar field and it fixed the issue.

BTW - any sort of Forum or Blog I'd be able to post some of the issues I've had to deal with in using OMPM so others don't have to waste a week or so with some of the "unwritten" issues that I've had?