There's some information missing in your question.
- Are you NATing traffic inside the IPSEC Tunnel
- Are you also managing the peer at the other end of the IPSEC Tunnel
Assuming you are not NATing the traffic in the IPSEC tunnel, this is a quick checklist.
Add the 10.41.41.x subnet to your Interesting traffic
This will indicate that the 10.41.41.x subnet is expected to transit in the IPSEC Tunnel.
You have to make that configuration change on both devices at each end of the IPSEC tunnel.
If this is not done properly, your VPN wont even be able to complete Phase 1 of the IPSEC tunnel.
Make sure your SSL VPN sends a proper route to the clients. This mean that the clients should have a route for the 172.29.112.x when connecting to the SSL VPN.
The same is true on the 172.29.112.x network, it needs to know where to route packets to 10.41.41.x .
In some cases, for example if both peers on the IPSEC VPN are also the default routers on their respective network, it might not be needed.
I'm not a Fortinet expert but most firewall will also require that you explicitly allow traffic inside a VPN tunnel with policies or ACLs. This is true for both the IPSEC Tunnel and the SSL VPN connectivity.
Like I said, this is a pretty vague answer (i.e. they are pointers) but since there's not much specifics in the question, it's the best I can think of.