Opened 7 years ago

Closed 3 years ago

#1695 closed defect (worksforme)

WinGRASS does not launch

Reported by: TheloniusMonk Owned by: grass-dev@…
Priority: major Milestone: 6.4.6
Component: Startup Version: 6.4.2
Keywords: launch, wingrass Cc:
CPU: x86-64 Platform: MSWindows 7

Description

I just installed GrassGIS (6.4.2.2; 6.4.2.1 and 6.4.1.1). If i try to start the program I always receive the following error-messages:

g.dirseps.exe - Application Error g.gisenv.exe - Application Error clean_temp.exe - Application Error python.exe - Application Error

Every error message comes with the following text:

"The application was unable to start correctly (0xc0000022). Click OK to close the application."

I already treid to install it into a folder without spaces (D:/data/GRASS) and installed the latest Microsoft NET framework package. But the problem did not get fixed.

Best regards Alex

Change History (12)

comment:1 Changed 7 years ago by marisn

Please check also Your home folder for any non-latin letters (i.e. C:\users\Māris would cause failure). Also worth to check if Your antivirus software isn't messing with GRASS during installation. Usually to install GRASS or QGIS I have to disable Comodo antivirus and defence+ Just temporary disable antivirus software and reinstall GRASS. Do not disable firewall, as GRASS installs just fine with firewall running and disabling firewall might leave Your computer vulnerable to network viruses.

Also check if there isn't more information in "advanced" part of error message.

comment:2 Changed 7 years ago by neteler

Can you please try a more recent installer (see also the comment above)?

http://wingrass.fsv.cvut.cz/grass64/

comment:3 Changed 7 years ago by spdj

CPU: Unspecifiedx86-64

Same here on Windows 7 (64bit!). Using the ProzessMonitor? we found a missing read access to a DLL.

Check access rules of:

  • windows/SysWOW64/msvcr71.dll

comment:4 in reply to:  3 Changed 7 years ago by hamish

Keywords: wingrass added

Replying to spdj:

Same here on Windows 7 (64bit!). Using the ProzessMonitor? we found a missing read access to a DLL.

could you explain the process of doing that?

Check access rules of:

  • windows/SysWOW64/msvcr71.dll

see also #1428

yesterday when pressing esc-enter I got an application error with set_data.exe when starting from the DOS command line startup icon on Windows7, I'm not sure if that's related or something else. (grass seemed to start ok after ack, anyway)

Hamish

comment:5 in reply to:  3 Changed 7 years ago by neteler

Replying to spdj:

Same here on Windows 7 (64bit!). Using the ProzessMonitor? we found a missing read access to a DLL.

Could you try this update?

http://www.microsoft.com/en-us/download/details.aspx?id=30679 "Visual C++ Redistributable for Visual Studio 2012 Update 1"

comment:7 Changed 7 years ago by hamish

It might be worth spending a bit of time with Dependency Walker exploring to see which of python.exe or wx.dll or gdal.dll or ... is responsible for the new msvr100 dependency.

dep. walker: http://grasswiki.osgeo.org/wiki/Bugs#Using_ldd

Hamish

comment:8 Changed 7 years ago by hamish

Component: DefaultStartup
Summary: GRASSGIS does not launchWinGRASS does not launch

comment:9 in reply to:  2 Changed 6 years ago by hamish

neteler asked:

Can you please try a more recent installer (see also the comment above)? http://wingrass.fsv.cvut.cz/grass64/

ping?

it should be fixed now if you select the install "important microsoft runtime libraries" button during installation.

Hamish

comment:10 Changed 6 years ago by neteler

No feedback, assuming that the new install "important microsoft runtime libraries" button helps.

Closing, feel free to reopen if the problem persists.

comment:11 Changed 3 years ago by neteler

Milestone: 6.4.36.4.6

comment:12 in reply to:  10 Changed 3 years ago by marisn

Resolution: worksforme
Status: newclosed

Replying to neteler:

No feedback, assuming that the new install "important microsoft runtime libraries" button helps.

Closing, feel free to reopen if the problem persists.

Still open? Closing for good.

Note: See TracTickets for help on using tickets.