Troubleshooting NEOSYS Timesheets system - Revision history

Arvind: /* Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can.” */

2016-01-28T10:48:47Z

Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can.”

← Older revision		Revision as of 10:48, 28 January 2016
Line 41:		Line 41:
	===Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can.”===		===Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can.”===

	Users MUST enter timesheets on a regular basis because NEOSYS restricts ~~user~~ to enter timesheets prior to the [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Timesheets_System#Maximum_Working_Days_Delay maximum working days delay] set in timesheet configuration file. If timesheet users want to enter timsheets prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has the authorisation to access all timesheet users' timesheet files, so the timesheet administrator can fill the same for them.		Users MUST enter timesheets on a regular basis because NEOSYS restricts users to enter timesheets prior to the [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Timesheets_System#Maximum_Working_Days_Delay maximum working days delay] set in timesheet configuration file.

			If timesheet users want to enter timsheets prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has the authorisation to access all timesheet users' timesheet files, so the timesheet administrator can fill the same for them.

	[[image:taerro.jpg]]		[[image:taerro.jpg]]

Arvind: /* Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can” */

2016-01-28T10:34:55Z

Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can”

← Older revision		Revision as of 10:34, 28 January 2016
Line 39:		Line 39:


	===Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator ~~can”~~===		===Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can.”===

	Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Timesheets_System#Maximum_Working_Days_Delay maximum working days delay] set in timesheet configuration file. If timesheet users want to enter timsheets prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has authorisation to access all timesheet users' timesheet files, ~~users can enter their timesheet with this access or~~ timesheet administrator can fill the same for them.		Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Timesheets_System#Maximum_Working_Days_Delay maximum working days delay] set in timesheet configuration file. If timesheet users want to enter timsheets prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has the authorisation to access all timesheet users' timesheet files, so the timesheet administrator can fill the same for them.

	[[image:taerro.jpg]]		[[image:taerro.jpg]]

Arvind: /* Error: “ Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administraor can” */

2016-01-28T08:56:16Z

Error: “ Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administraor can”

← Older revision		Revision as of 08:56, 28 January 2016
Line 39:		Line 39:


	===Error: ~~“ Sorry~~, you cannot enter or edit timesheets older than X working days. Your timesheet ~~administraor~~ can”===		===Error: “Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administrator can”===

	Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the maximum working days delay set in timesheet configuration file. If timesheet users want to enter ~~timsheet~~ prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has authorisation to access all timesheet ~~user~~'s timesheet ~~file~~, users can enter their timesheet with this access or timesheet administrator can fill the same for them.		Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Timesheets_System#Maximum_Working_Days_Delay maximum working days delay] set in timesheet configuration file. If timesheet users want to enter timsheets prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has authorisation to access all timesheet users' timesheet files, users can enter their timesheet with this access or timesheet administrator can fill the same for them.

	[[image:taerro.jpg]]		[[image:taerro.jpg]]

Priyanka at 07:26, 28 January 2016

2016-01-28T07:26:38Z

← Older revision		Revision as of 07:26, 28 January 2016
Line 30:		Line 30:

	Once you determine that there is a problem in the connectivity and other locations/clients are not facing the same then contact the IT administrator of that client/network and probe if they have outgoing ports (2500 in this case) blocked or filtered on their firewall.		Once you determine that there is a problem in the connectivity and other locations/clients are not facing the same then contact the IT administrator of that client/network and probe if they have outgoing ports (2500 in this case) blocked or filtered on their firewall.
			Error: “ Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administraor can”

			Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the maximum working days delay set in timesheet configuration file. If timesheet users want to enter timsheet prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has authorisation to access all timesheet user's timesheet file, users can enter their timesheet with this access or timesheet administrator can fill the same for them.
	If the connectivity is problem free then Timesheet Approval Mails should be send out Manually.		If the connectivity is problem free then Timesheet Approval Mails should be send out Manually.
	To do so select Menu-> Timesheet -> Timesheet Printout and select the option Approval Emails to send out the mails again.		To do so select Menu-> Timesheet -> Timesheet Printout and select the option Approval Emails to send out the mails again.

	[[image:timesheetapproval.jpg]]		[[image:timesheetapproval.jpg]]


			===Error: “ Sorry, you cannot enter or edit timesheets older than X working days. Your timesheet administraor can”===

			Users MUST enter timesheets on a regular basis because NEOSYS restricts user to enter timesheets prior to the maximum working days delay set in timesheet configuration file. If timesheet users want to enter timsheet prior to maximum working days delay then they MUST contact their Timesheet administrator as the error message says. Timesheet administrator has authorisation to access all timesheet user's timesheet file, users can enter their timesheet with this access or timesheet administrator can fill the same for them.

			[[image:taerro.jpg]]

Arvind: /* Troubleshooting why a user isn’t getting timesheets reminder emails */

2015-10-04T12:51:43Z

Troubleshooting why a user isn’t getting timesheets reminder emails

← Older revision		Revision as of 12:51, 4 October 2015
Line 2:		Line 2:
	#No email address.		#No email address.
	#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com		#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com
	#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solving_NEOSYS_smtp_server_failure\|Resolving NEOSYS SMTP Failure]		#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solving_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]
	#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.		#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
	#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.		#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.

Vineet at 09:03, 17 April 2012

2012-04-17T09:03:39Z

← Older revision		Revision as of 09:03, 17 April 2012
Line 2:		Line 2:
	#No email address.		#No email address.
	#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com		#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com
	#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [[Troubleshooting_NEOSYS_Generally#Solving_NEOSYS_smtp_server_failure\|Resolving NEOSYS SMTP Failure]]		#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [http://techwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solving_NEOSYS_smtp_server_failure\|Resolving NEOSYS SMTP Failure]
	#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.		#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
	#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.		#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.

Vineet at 09:01, 17 April 2012

2012-04-17T09:01:25Z

← Older revision		Revision as of 09:01, 17 April 2012
Line 2:		Line 2:
	#No email address.		#No email address.
	#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com		#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com
	#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [[Troubleshooting_NEOSYS_Generally#~~Solution_to_NEOSYS_smtp_server_failure~~\|Resolving NEOSYS SMTP Failure]]		#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [[Troubleshooting_NEOSYS_Generally#Solving_NEOSYS_smtp_server_failure\|Resolving NEOSYS SMTP Failure]]
	#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.		#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
	#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.		#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.

Vineet at 07:19, 15 February 2012

2012-02-15T07:19:13Z

← Older revision		Revision as of 07:19, 15 February 2012
Line 2:		Line 2:
	#No email address.		#No email address.
	#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com		#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com
	#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [~~http://userwiki.neosys.com/index.php/~~Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]		#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [[Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure\|Resolving NEOSYS SMTP Failure]]
	#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.		#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
	#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.		#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.

Vineet at 13:25, 16 January 2012

2012-01-16T13:25:05Z

← Older revision		Revision as of 13:25, 16 January 2012
Line 1:		Line 1:
	=== Troubleshooting why a user isn’t getting timesheets reminder emails ===		=== Troubleshooting why a user isn’t getting timesheets reminder emails ===
	* No email address.		#No email address.
	* Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com~~. Note that, in the usual case, the~~ NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.		#Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com
	* Check the user has logged in at least once in the last 31 days otherwise no emails are sent.		#The standard NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.<br>In case of repeated email failure using neosys smtp server, you can alternatively use the client's smtp server to send emails. See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]
	* Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.		#Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
	* Timesheets are not sent if User is authorised to do “TIMESHEET AVOID REMINDERS”		#Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.
	* User is not authorised to do "TIMESHEET ACCESS”		#Timesheets are not sent if User is authorised to do “TIMESHEET AVOID REMINDERS”
	* User is the bottom user of a group. Create a “departmental” user below them.		#User is not authorised to do "TIMESHEET ACCESS”
	* Timesheet is before the start date specified in the Timesheet Configuration File		#User is the bottom user of a group. Create a “departmental” user below them.
	* User is a timesheet administrator		#Timesheet is before the start date specified in the Timesheet Configuration File
			#User is a timesheet administrator

	=== Troubleshooting a user getting timesheets reminder emails for others ===		=== Troubleshooting a user getting timesheets reminder emails for others ===
Line 34:		Line 35:

	[[image:timesheetapproval.jpg]]		[[image:timesheetapproval.jpg]]

	~~=== No Timesheet Approval/Reminder Emails due to NEOSYS SMTP Server Failure ===~~
	~~See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]~~

Vineet: /* NEOSYS SMTP Server Failure */

2012-01-16T12:46:12Z

NEOSYS SMTP Server Failure

← Older revision		Revision as of 12:46, 16 January 2012
Line 35:		Line 35:
	[[image:timesheetapproval.jpg]]		[[image:timesheetapproval.jpg]]

	=== NEOSYS SMTP Server Failure ===		=== No Timesheet Approval/Reminder Emails due to NEOSYS SMTP Server Failure ===
	See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]		See [http://userwiki.neosys.com/index.php/Troubleshooting_NEOSYS_Generally#Solution_to_NEOSYS_smtp_server_failure Resolving NEOSYS SMTP Failure]