Expiration policy not routing documents

I had a SP 2010 environment that I upgraded to 2013 but kept in 2010 mode.
I created a content type for record handling. I created a retention policy based on a certain date that would route documents to a graveyard library.
Testing in dev and test environment was successful. However, in production it is not. The timer jobs run successfully. I can even notice that after the last timer job runs, the graveyard library has a modified time of a couple of minutes but no documents
in the library.
I have tested the Send To connection successfully. Content Organizer rule is working. Features are activated. Searching through the logs, found the attached. Any ideas or questions, please ask as this was the main reason in choosing SharePoint in my organization.

Can you paste the log details to this post. If possible, send me the whole file
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

Similar Messages

Retention Processing does not move Document Set to the Drop Off Library

Hi Everyone.
Had Retention Processing working fine. Moving files between Document Librarys and the Record Centre using Information Management Policies to move to the Drop-Off Library where the Content Organizer Rules moved them to the relevent Library.
It has all come to a grinding halt with the following line in the '14 hive' logs.
Skipping retention processing for item /doc/Housing/1 RET TEST SET on web http://moraysrv052/doc because there is an unprocessed schedule update. 1b1dfe42-28f9-440a-b84a-17c20aa9c7d6
I have searched the Internet and these forums but can find no reference to this error, Can anyone help as automatic retention policies are crucial to our Sharepoint Implementation.
Cheers
Ross Urquhart

Vinit
Thanks for the advise but not the answer unfortunately.
I have the Content Organizer & Expiration Policy Timer Jobs running every 15 mins, Information Management Policy runs Weekly as this only effects changes to Policy. I have changed the times so all jobs run every 15 mins. Still get the same error message.
Expiration worked perfectly before when it was triggered by Closure Date, A column we created which the user populates to indicate the Document can be closed. Retention then moves the Document to the Record Centre. I changed the trigger on one of the Document
Sets to be Created Date and this generates the error, Change this back to Closure Date, no error, Document moves to Record Centre Drop Off Library.
Another observation. If Retention is against a any other Content Type it is called Created if it is against a Document Set Content Type it is called Created Date, however when you review the Compliance Details of the Set it is called Created.
Does this trigger any ideas.
Cheers
Ross Urquhart

Problem routing documents with Content Organizer Timer Job

Hi,
We have a farm that has two front-end servers with SharePoint Server 2010 Standard and one back-end with SQL Server 2008 R2. We are using a multiple site collections with the record center template to route documents in different document libraries. The farm
has SP1 and cumulative update of December 2012.
The problem is that the Content Organizer Job cannot route documents in a one of the sites, and reports the error in the log: “Routing Engine: Rule 'Move_Document' incorrectly specified the target folder /sites/Energy/DocumentLibrary was not found”. This is
happening only in one of the front-ends, because, if the other front-end runs the job for this specific site, the problem doesn't replicate.
We try to restart the two front-ends, and restart the SharePoint Timer 2010 service, but none of the solutions corrects the problem.
Thanks for your help

Do you have NLB in use and are you using Kerberos authentication? My gut feel is that you might have issues where one WFE is trying to work with the other one but is failing to authenticate for some reason.
Try logging onto each box and browsing to the sites given as the timer service user identity, see if you can browse to the site.

Policy based routing on VRF interfaces to route traffic through TE Tunnel

Hi All,
Is there a method to do policy based routing on VRF interfaces and route data traffic through one TE tunnel and non-data traffic through another TE tunnel.
The tunnel is already build up with these below config
interface Tunnel25
ip unnumbered Loopback0
tunnel destination 10.250.16.250
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name test
ip explicit-path name test enable
next-address x.x.x.x
next-address y.y.y.y
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
mpls traffic-eng tunnels
nterface GigabitEthernet5/2
mpls traffic-eng tunnels
mpls ip
Is there additional config needed to work ,also in the destination end for the return traffic,we want to use the normal PATH --I mean non TE tunnel.
We tested with the above scenario,but couldn't able to reach the destination.Meantime we had a question,when the packet uses the policy map while ingress,it may not know the associatuion with VRF(Is that right? --If so ,how to make it happen)
Any help would be really appreciated
Thanks
Regards
Anantha Subramanian Natarajan

hi Anantha!
I might not be the right person to comment on your first question. I have not configured MVPNs yet and not very confertable with the topic.
But I am sure that if you read through the CBTS doc thoroughly, you might be able to derive the answer yourself. One thing I notice is that " a Tunnel will be selected regularly according to the routing process (even isf it is cbts enabled). From the tunnels selected using the regular best path selection, the traffic is mapped to a perticular tunnel in the group if specific class is mapped to that tunnel.
So a master tunnel can be the only tunnel between the 2 devices over which the routing (bgp next hops) are exchanged and all other tunnels can be members of this tunnel. So your RPF might not fail.
You might have to explore on this a bit more and read about the co-existance of multicast and TE. This will be the same as that.
For your second question, the answer would be easy :
If you want a specific eompls cust to take a particular tunnel/path, just create a seperate pair of loopbacks on the PEs. Make the loopback learnt on the remote PE through the tunnel/path that you want the eompls to take. Then establish the xconnect with this loopback. I am assuming that your question is that a particular eompls session should take a particular path.
If you meant that certain traffic from the same eompls session take a different path/tunnel, then CBTS will work.
Regards,
Niranjan

Policy Based Routing with VPN Client configuration

Hi to all,
We have a Cisco 2800 router in our company that also serves as a VPN server. We use the VPN Client to connect to our corporate network (pls don't laugh, I know that it is very obsolete but I haven't had the time lately to switch to SSL VPN).
The router has two WAN connections. One is the primary wan ("slow wan" link with slower upload 10D/1U mbps) and it is used for the corporate workstations used by the emploees. The other is our backup link. It has higher upload speed - 11D/11U mbps, (fast wan), and thus we also use the high upload link for our webserver (I have done this using PBR just for the http traffic from the webserver). For numerous other reasions we can not use the `fast wan` connection as our primary connection and it is used anly as a failover in case the primary link fails.
The `fast wan` also has a static IP address and we use this static IP for the VPN Client configuration.
Now the thing is that because of the failover, when we connect from the outside using the VPN Client, the traffic comes from the`fast wan` interface, but exits from the `slow wan` interface. And because the `slow wan` has only 1mbps upload the vpn connection is slow.
Is there any way for us to redirect the vpn traffic to always use the `fast wan` interface and to take advantage of the 11mbps upload speed of that connection?
This is our sanitized config
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp client configuration group dc
key ***
dns 192.168.5.7
domain corp.local
pool SDM_POOL_1
acl 101
max-users 3
netmask 255.255.255.0
crypto isakmp profile sdm-ike-profile-1
   match identity group dc
   isakmp authorization list sdm_vpn_group_ml_1
   client configuration address respond
   virtual-template 1
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec profile SDM_Profile1
set security-association idle-time 3600
set transform-set ESP-3DES-SHA
set isakmp-profile sdm-ike-profile-1
interface Loopback0
ip address 10.10.10.1 255.255.255.0
interface FastEthernet0/0
description *WAN*
no ip address
ip mtu 1396
duplex auto
speed auto
interface FastEthernet0/0.3
description FAST-WAN-11D-11U
encapsulation dot1Q 3
ip address 88.XX.XX.75 255.255.255.248
ip load-sharing per-packet
ip nat outside
ip virtual-reassembly
interface FastEthernet0/0.4
description SLOW-WAN-10D-1U
encapsulation dot1Q 4
ip address dhcp
ip nat outside
ip virtual-reassembly
no cdp enable
interface FastEthernet0/1
description *LOCAL*
no ip address
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1.10
description VLAN 10 192-168-5-0
encapsulation dot1Q 10
ip address 192.168.5.1 255.255.255.0
ip nat inside
ip virtual-reassembly max-reassemblies 32
no cdp enable
interface FastEthernet0/1.20
description VLAN 20 10-10-0-0
encapsulation dot1Q 20
ip address 10.10.0.254 255.255.255.0
ip access-group PERMIT-MNG out
ip nat inside
ip virtual-reassembly
!!! NOTE: This route map is used to PBR the http traffic for our server
ip policy route-map REDIRECT-VIA-FAST-WAN
no cdp enable
interface Virtual-Template1 type tunnel
ip unnumbered Loopback0
tunnel mode ipsec ipv4
tunnel protection ipsec profile SDM_Profile1
interface Virtual-Template3
no ip address
interface Virtual-Template4
no ip address
ip local pool SDM_POOL_1 192.168.5.150 192.168.5.152
ip forward-protocol nd
!!! SLOW-WAN NEXT HOP DEFAULT ADDRESS
ip route 0.0.0.0 0.0.0.0 89.XX.XX.1 5
!!! FAST-WAN NEXT HOP DEFAULT ADDRESS
ip route 0.0.0.0 0.0.0.0 88.XX.XX.73 10
ip nat inside source route-map FAST-WAN-NAT-RMAP interface FastEthernet0/0.3 overload
ip nat inside source route-map SLOW-WAN-NAT-RMAP interface FastEthernet0/0.4 overload
access-list 101 remark SDM_ACL Category=4
access-list 101 permit ip 192.168.5.0 0.0.0.255 any
access-list 101 permit ip 10.10.0.0 0.0.0.255 any
ip access-list extended FAST-WAN-NAT
permit tcp 192.168.5.0 0.0.0.255 range 1025 65535 any
permit udp 192.168.5.0 0.0.0.255 range 1025 65535 any
permit icmp 192.168.5.0 0.0.0.255 any
permit tcp 10.10.0.0 0.0.0.255 range 1025 65535 any
permit udp 10.10.0.0 0.0.0.255 range 1025 65535 any
permit icmp 10.10.0.0 0.0.0.255 any
ip access-list extended REDIRECT-VIA-FAST-WAN
deny   tcp host 10.10.0.43 eq 443 9675 192.168.5.0 0.0.0.255
permit tcp host 10.10.0.43 eq 443 9675 any
ip access-list extended SLOW-WAN-NAT
permit ip 192.168.5.0 0.0.0.255 any
permit ip 10.10.0.0 0.0.0.255 any
route-map FAST-WAN-NAT-RMAP permit 10
match ip address FAST-WAN-NAT
match interface FastEthernet0/0.3
route-map REDIRECT-VIA-FAST-WAN permit 10
match ip address REDIRECT-VIA-FAST-WAN
set ip next-hop 88.XX.XX.73
route-map SLOW-WAN-NAT-RMAP permit 10
match ip address SLOW-WAN-NAT
match interface FastEthernet0/0.4

Can you try to use PBR Match track object,
Device(config)# route-map abc
Device(config-route-map)# match track 2
Device(config-route-map)# end
Device# show route-map abc
route-map abc, permit, sequence 10
Match clauses:
track-object 2
Set clauses:
Policy routing matches: 0 packets, 0 bytes
Additional References for PBR Match Track Object
This feature is a part of IOS-XE release 3.13 and later.
PBR Match Track Object
Cisco IOS XE Release 3.13S
The PBR Match Track Object feature enables a device to track the stub object during Policy Based Routing.
The following commands were introduced or modified: match track tracked-obj-number
Cheers,
Sumit

Urgent help -can not access Documents (windows 7)

After some one renamed one profile and my documents (roaming profile and my documents redirected to network path too through group policy). Now , I can not open Documents. I got this message: "can't open this item It might have been
moved, renamed, or deleted. Do you want to remove this item?"
Thank you.

After some one renamed one profile and my documents (roaming profile and my documents redirected to network path too through group policy). Now , I can not open Documents.
Since you have a roaming profile, you must be connected to a Windows server. If so then you should discuss this problem with your network administrator.

Apply password period expire policy to resource accounts

Hi! In IDM 7.1 I know can apply Password Period Expire Policy to Lighthouse account. It's simple and It works so well.
But, I ' d like to know how can I apply a password period expire policy to resource accounts to synchronize as Lighthouse as resources accounts (i.e. LDAP accounts, etc.).
I knew in previous versions of IDM wasn't possible.
Thanks.

Figures the solution form my own Q....
I had pass through configured with LDAP to a login module group - which had the following as the order.
1. LDAP
2. IDM
As LDAP resource adaptor does not support expiry, we have to look for the IdM Expiry. so i reversed the order so that IdM takes precedence in resolving the value of 'loginwarning" on the end user dashboard.
Anyways in my environment, All password resets are handled from IdM so the Pass through wont hurt.

Policy based routing to host in same vlan/subnet

Hello i have nexus 7k that i have a policy based routing setup as follows for 2 vlans, 802 and 803, to set default route out to a host in vlan 802. i have applied my policy to the vlans and everything works fine for a host in vlan 803, it routes over and out properly. However when im in vlan 802 my host traffic never gets to 172.21.1.237 when pointed at the gateway 172.21.1.1. I can see the pbr statistics incrementing indicating that i am initially hitting the policy but im not sure where my traffic goes after that. I can talk to .237 direct in the vlan but i would like this to work through pbr to utilize all of my other routes and default gateway.
vlans 802
172.21.1.1/24
ip policy route-map West
vlan 803
172.21.17.1/24
ip policy route-map West
route-map West permit 10
match vlan 802-803
set ip default next-hop 172.21.1.237
Im thinking there is some kind of hairpinning problem or maybe im creating some kind of blackhole.
any help is appreciated.
thanks, scott

Scott
If the destination IP is in the same subnet as source IP then it won't be routed it will be L2 switched so it would never use the default gateway ie.
src IP 172.21.1.10 255.255.255.0
dst IP 172.21.1.237 255.255.255.0
src compares it's own IP with it's subnet mask and sees it is on the 172.21.1.x network. src then compares the destination IP with it's own subnet mask and sees it is also on the 172.21.1.x network so it simply arps out for that address and when it gets the mac address it sends it direct to the destination. It would only use the default gateway if the destination IP was on a different network.
So i don't see how you will be able to do this and i'm not sure why you are seeing hits in your PBR acl for the host in the 172.21.1.x network.
Edit - what exactly do you mean when you say -
However when im in vlan 802 my host traffic never gets to 172.21.1.237 when pointed at the gateway 172.21.1.1.
How are you doing this ie. pointing it to the default gateway because as i say it should always be able to communicate with 172.21.1.237 as it is in the same subnet.
Jon

Policy based routing on a Layer 3 switch

I am doing some lab testing on policy based routing. I am having some issues that I can't see to get working right.
Here is the config:
ip local policy route-map Test-map
ip access-list extended icmp
permit icmp 192.168.1.0 0.0.0.255 192.168.200.0 0.0.0.255
permit icmp 192.168.2.0 0.0.0.255 192.168.200.0 0.0.0.255
ip access-list extended telnet
permit tcp 192.168.1.0 0.0.0.255 192.168.200.0 0.0.0.255 eq telnet
permit tcp 192.168.2.0 0.0.0.255 192.168.200.0 0.0.0.255 eq telnet
ip access-list extended test
permit icmp 192.168.1.0 0.0.0.255 192.168.200.0 0.0.0.255
route-map Test-map permit 10
match ip address icmp
set ip next-hop 192.168.1.3
route-map Test-map permit 20
match ip address telnet
set ip next-hop 192.168.1.2
The first thing I did was I only had 1 network on this box the 192.168.1.x and when I plugged a pc into a port on the switch and tried to ping the remote network of 192.168.200.1 it will not hit on my access-lists for my policy based routes.
If I do a ping from the switches IOS interface directly the access-lists get hits and the policy based routes work fine.
So I was puzzled by this and figured maybe policy based routes only work if they come from one network to another network. So I setup a 2nd vlan called 192.168.2.x and put my pc in that vlan. I then proceed to ping 192.168.200.1 and still was unable to get any hits on the access-lits or policy based routes.
So what am I doing wrong or am I trying to use policy based routing wrong here?

I've done that command but then when I do a "show run" I don't see it in the configuration and it doesn't seem to be working.
Also if everything is on the same vlan 100 will the pbr work? or does this require that I use two different vlans? (one for inside and one for outside) so that I have a interface from where the packets are coming from?

WSA and Cisco Policy Based Routing

I'm looking to convert my WSA from explicit to transparent proxy using policy based routing on a Cisco router. See the config below where xxx.xxx.xxx.xxx is the P1 interface on the WSA. Does anyone see any issues with the following in a production environment?
access-list 110 permit tcp any any eq www
route-map proxy-redirect permit 10
match ip address 110
set ip next-hop xxx.xxx.xxx.xxx
interface ethernet0/1
ip policy route-map proxy-redirect
The P1 interface on the WSA is located upstream from the router so I'm not checking for it in the ACL.

That router configuration looks good to me, but just make sure that the WSA was configured for Transparent mode during the initial System Setup Wizard configuration. If it was initially configured for explicit only, then you will need to run the wizard again to change it to transparent.
Also, make sure to add a deny statement to the top of access-list 110 for the WSA IP address if the WSA will be going out to the Internet through the same e0/1 interface. Loops are bad. :twisted:
Cheers,
Jason

SRP527-U Policy Based Routing To Squid?

Hi,
I have a SRP527-U running 1.2.6.
I have a simple setup, a ADSL connection to the Internet and a bunch of PC's behind that with Internet access.
I've setup a host on the same VLAN as the other devices and I've set it up running squid.
What I'd like to do is use the Policy Based Routing function to force all users trying to browse the Internet through that squid instance.
That is
Source of 192.168.0.20/32 Port 80 -> Policy Based Route to Destination of 192.168.0.50 port 3128
Is that possible with this device, or is that outside of its capabilities? I've looked at the PBR section, but it seems to imply forcing all traffic out through a WAN Interface which isn't what I want to achieve.
Kind Regards,
Tim

Scott
If the destination IP is in the same subnet as source IP then it won't be routed it will be L2 switched so it would never use the default gateway ie.
src IP 172.21.1.10 255.255.255.0
dst IP 172.21.1.237 255.255.255.0
src compares it's own IP with it's subnet mask and sees it is on the 172.21.1.x network. src then compares the destination IP with it's own subnet mask and sees it is also on the 172.21.1.x network so it simply arps out for that address and when it gets the mac address it sends it direct to the destination. It would only use the default gateway if the destination IP was on a different network.
So i don't see how you will be able to do this and i'm not sure why you are seeing hits in your PBR acl for the host in the 172.21.1.x network.
Edit - what exactly do you mean when you say -
However when im in vlan 802 my host traffic never gets to 172.21.1.237 when pointed at the gateway 172.21.1.1.
How are you doing this ie. pointing it to the default gateway because as i say it should always be able to communicate with 172.21.1.237 as it is in the same subnet.
Jon

Can I apply a Rights Management policy to multiple documents in a folder at the same time using Adobe Acrobat Pro?

How can I apply a single Rights Management Policy to multiple documents in a folder at the same time instead of applying it to each document individually?

I don't know of a method with Acrobat, why not set up a watch folder and just drop all the files in that folder to have rights applied. You might want to look at the workbench help if you've not done this before.

JAAS-File policy not effect !

I were read "the JAAS tutorial". If I use command line, all things ok ! But when I use Eclipse to compile, file policy not effect ! Do I need modify file "java.security" inside jre/lib/security" ?.
The file policy is : sampleazn.policy :
========
grant codebase "file:/C:/Documents and Settings/quoc thai/Auth/bin/sample/module/*" {
permission javax.security.auth.AuthPermission "modifyPrincipals";
grant codebase "file:/C:/Documents and Settings/quoc thai/Auth/bin/sample/*" {
permission javax.security.auth.AuthPermission "createLoginContext.Sample";
permission javax.security.auth.AuthPermission "doAsPrivileged";
grant codebase "file:/C:/Documents and Settings/quoc thai/Auth/bin/sample/*",
Principal sample.module.SamplePrincipal "testUser" {
permission java.util.PropertyPermission "java.home", "read";
permission java.util.PropertyPermission "user.home", "read";
=========
The file config :
Sample {
sample.module.SampleLoginModule required debug=true;
==========
Please help me to configure file policy !!!
Thank every one !!

Dave,
I just tried this on my test zlm server and that work the following way:
1. create a text file policy with the following parameters:
file name: /etc/login.defs
change name: modify login.defs
Change mode: Search file
Search string: ^PASS_MAX_DAYS 99999
Take care that there is a tab between the PASS.. and the number ! If you are not sure if you have just white spaces there or a tab, open it with a editor and check it. The character ^ stands for the beginning of the line, so this will match just the one line with that string. This is a normal regular expression. If you have systems with different entries you can also just enter ^PASS_MAX_DAYS and it will match all of them, then it is independent if there are tabs or white spaces there in.
Result action: Replace line
New string: PASS_MAX_DAYS 12345
The rest of the parameters can remain on the default values. Assign it and after the next refresh of the device, the policy should be applied and you should see the new valu.
Rainer

Unable to run Information Management Policy &Expiration Policy Timer services

I have set the retention policy of a list and need to run Information Management Policy and Expiration Policy timer jobs but when I went to central Admin and try to run now its not running.I changed the scheduled to run from weekly to daily and scheduled
it to run even that did not work.I also tried hourly but still unable to run the timer job.
Its not that the timer job has never run.It shows last run a week ago when it was scheduled weekly but now its not running at all.
Any idea what could be causing this?Or I am missing something?

Hello,
Which job is running first? You need to set recurring Schedule in such a way that "Information management policy" job should run before the "Expiration policy".
Also check ULS log for more information about issue.
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

Policy base routing in asa

hi
i attach picture
i want answer to any user from the same router
example :
request user1 from isp1 , i answer it from same isp1 router
i think asa dose not support pbr ,, please help me with same senario .

policy-based routing, similar to what an IOS router can do based on incoming traffic and then overriding the routing table for the next hop, isn't a feature in the ASA.
We can do policy based NAT, inspection and filtering, but not policy based routing.

Expiration policy not routing documents

Similar Messages

Maybe you are looking for