cancel
Showing results for 
Search instead for 
Did you mean: 

FSL-02013 Unable to access file sapevents.dll

Former Member
0 Kudos

Hi,

I am applying patch SP 12 to SAP WAS 640 Java.During the third step..that is SP system installation i get error as FSL-02013 Unable to access file ....sapevents.dll

I am login as <SAPSID>adm which is member of administrator group.

Do i have to be administrator user to run the installation?

Can some one helpout in this?

Deepti Patil

Accepted Solutions (1)

Accepted Solutions (1)

guru_subramanianb
Active Contributor
0 Kudos

Hi,

I think u shd login with admin userid and install the same.

Rdgs,

G

Former Member
0 Kudos

Hi G,

Thanks

but before that i found in MMC Console I couldnt see any instances, SAP MMC services were disabled.

I restarted the server but we had to restart the services manually.

After that we could see the instances but J2EE Server is RED , jcontrol.exe Server could nnot be started.

Pls help me on this urgently.

Thanks

Deepti Patil

Former Member
0 Kudos

Hi Deepthi,

Please rename the sapevents.dll at your OS level to sapevents2.dll and restart the installation.

regards

Anand.M

Former Member
0 Kudos

Hi Anand,

Already tried that , its not working.

Thanks

Pls reply

Deepti

Former Member
0 Kudos

Hi Deepthi,

Can you please check the error again? It will have the source and destination target(folders). Copy it manually and try.

regards

Anand.M

Former Member
0 Kudos

Hey anand that worked, hopeflly it shd work fine now...

Former Member
0 Kudos

Hi Deepti,

Nice to hear this. It will go smooth. don't worry.

enjoy with rest of the installation.

regards

Anand.M

Former Member
0 Kudos

Hi Anada,

SP19 update...

Had the same problem first with sapevents.dll and after a system restart with saposcol.exe

Renamed saposcol.exe and after the error it was there again so the copy process should have worked? Anyway, after copying saposcol.exe manually like you posted did the trick...

Regards.

Answers (2)

Answers (2)

Former Member
0 Kudos

In my case, running MOM service was cause of the error.

When I stopped it, installation continued...

Former Member
0 Kudos

Try to see if there is a process runnig of that dll

programs like procexp can find processes by .dll files.

After you find it stop it and retry the installation.