Can't connect for updates still?

EvilDrK · June 18th, 2014, 09:26 AM

OK so it looks like there's some troubles connecting with the updates site. And since I'm running HL under linux/wine I'm sure that's not helping matters. Is anyone else still having troubles? Any ideas how to get around them?

charlieluce · June 18th, 2014, 04:14 PM

I just tried it in Windows 7 and was able to update for Hero Lab 5.2b without a problem.

Mathias · June 18th, 2014, 04:38 PM

In the Tools menu, choose "Diagnostics", and then "Check Internet Connection"

Do you get the following message:

Quote:

No problems could be found with your internet connection.

Retrieval from wolflair.com succeeded.
Retrieval from lonewolfdevel.com succeeded.

(I just tested it at 5:39PM, PST, and it works for me)

EvilDrK · June 19th, 2014, 09:29 AM

Trying to check the internet connection just hangs up for a long time.
Linux Mint 17 Qiana/ Ubuntu Trusty, Wine 1.6.2 running under Win 7 mode.
About 2 weeks ago then after trying it when I got from vacation and hadn't run it in a while it wasn't working. Think it's the certificate stuff most likely but don't have a clue how to fix it.

Mathias · June 19th, 2014, 09:37 AM

At this point, you're best off emailing support@wolflair.com. Our support people have more experience dealing with the way Hero Lab's internet connection works than I do.

EvilDrK · June 19th, 2014, 09:41 AM

**nods** have a ticket started. Thanks!

EvilDrK · June 20th, 2014, 05:38 AM

So while I'm annoyed by this, I wasn't worried all that much since the systems I wanted to work worked. Until I tried to load a M&M3 character today. Which wants to load some MECHA file (Portal 'mchTable' - Auto thing 'Mecha' not found) that it can't find now. So any insights - looks like the support folks don't really have a good idea either since they basically know the updates issue is with the cert for us Linux folks, but don't know how to get around it.

This is the output from the wine.log when I run wine HeroLab.exe >wine.log 2>&1

Code:

fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:GetCurrentHwProfileA (0x33fba0) semi-stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:win:RegisterDeviceNotificationA (hwnd=0x1b0b60, filter=0xe2e934,flags=0x00000001) returns a fake device notification handle!
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4910,(nil)): stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x00000013
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:netapi32:NetGetJoinInformation Semi-stub (null) 0xcae5f4 0xcae5ec
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x00000013
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   13 jjn3-322-mint.local. HINFO X86_64\00c2\00a6LINUX"
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd3c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 jjn3-322-mint.local. Addr 10.78.211.65"
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadcac,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"Local Hostname jjn3-322-mint.local already in use; will try jjn3-322-mint-2.local instead"
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   21 65.211.78.10.in-addr.arpa. PTR jjn3-322-mint.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd40,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding   23 65.211.78.10.in-addr.arpa. PTR jjn3-322-mint-2.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   21 7.4.f.1.1.4.e.f.f.f.5.e.7.6.2.d.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.
f.ip6.arpa. PTR jjn3-322-mint.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd40,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding   23 7.4.F.1.1.4.E.F.F.F.5.E.7.6.2.D.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F
.ip6.arpa. PTR jjn3-322-mint-2.local."
fixme:ras:RasEnumConnectionsW (0x1b0508,0x32cce8,0x76c623e4),stub!
fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
fixme:service:EnumServicesStatusW resume handle not supported
fixme:ras:RasEnumEntriesW ((nil),(null),0xbceada8,0x32d518,0xbceaa94),stub!
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae538,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub

If it helps I'm on Linux Mint Qiana / Ubuntu Trusty on one PC and Linux Mint Nadia / Ubuntu Precise on the other. Both are running Wine 1.62

TCArknight · June 20th, 2014, 09:16 AM

I forget which package it is, but I believe Mecha are part of a MnM 2E supplement. Maybe the character was 2E originally?

donaldrp · June 21st, 2014, 12:30 PM

Was there any resolution to your problem, also running Herolab under Wine in Linux. It was working fine until recently...

EvilDrK · June 24th, 2014, 03:52 PM

Might be haven't had a chance as I've been away from keyboard due to doing my civic duty on JD. http://forum.winehq.org/viewtopic.php?t=22746 is the wine forums post which says they have a bug started. The bug suggests a workaround but I have not tried it yet.

EvilDrK Junior Member Join Date: May 2014 Posts: 7 June 18th, 2014, 09:26 AM	OK so it looks like there's some troubles connecting with the updates site. And since I'm running HL under linux/wine I'm sure that's not helping matters. Is anyone else still having troubles? Any ideas how to get around them?
#1

charlieluce Senior Member Join Date: Jul 2008 Posts: 1,321 June 18th, 2014, 04:14 PM	I just tried it in Windows 7 and was able to update for Hero Lab 5.2b without a problem. Currently Running: Pathfinder Second Edition Currently Playing: Pathfinder First Edition, Star Trek Adventures Former HL Games: D&D 4e & 5e, Mutants & Masterminds 2E & 3E, Savage Worlds
#2

Mathias Senior Member Lone Wolf Staff Join Date: May 2005 Posts: 13,213 June 19th, 2014, 09:37 AM	At this point, you're best off emailing support@wolflair.com. Our support people have more experience dealing with the way Hero Lab's internet connection works than I do.
#5

TCArknight Senior Member Join Date: Jan 2007 Location: NW Arkansas Posts: 1,321 June 20th, 2014, 09:16 AM	I forget which package it is, but I believe Mecha are part of a MnM 2E supplement. Maybe the character was 2E originally?
#8

donaldrp Junior Member Join Date: Jun 2014 Posts: 2 June 21st, 2014, 12:30 PM	Was there any resolution to your problem, also running Herolab under Wine in Linux. It was working fine until recently...
#9